You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A suggested approach is to have process.env.TEST_TIMEOUT and a new process.env.TEST_TIMEOUT_LONG consistently applied across the project so that the GH Actions can be incremented without modifying code and local development can shorten a test run by decreasing the same environment variables on the local machine.
The text was updated successfully, but these errors were encountered:
The test suite currently defines a session timeout for tests based on
process.env.TEST_TIMEOUT
https://github.com/nodejs/llnode/blob/main/test/common.js#L173
This timeout has recently been incremented due to the restricted resources in GH Actions.
The timeout also isn't applied to all the tests and some have been overridden directly in the code base for longer tests.
llnode/test/plugin/workqueue-test.js
Line 29 in ff75da7
A suggested approach is to have
process.env.TEST_TIMEOUT
and a newprocess.env.TEST_TIMEOUT_LONG
consistently applied across the project so that the GH Actions can be incremented without modifying code and local development can shorten a test run by decreasing the same environment variables on the local machine.The text was updated successfully, but these errors were encountered: