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
The SIGKILL timeout is currently hardocoded in launcher\process.js file. On our CI build server, the process exit takes longer than 2 seconds when running large number of tests, as the process exit waits for all Chrome child processes to be killed.
The SIGKILL timeout is currently hardocoded in launcher\process.js file. On our CI build server, the process exit takes longer than 2 seconds when running large number of tests, as the process exit waits for all Chrome child processes to be killed.
Is it possible to make this timeout configurable?
The text was updated successfully, but these errors were encountered: