New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Print useful message when worker threads cannot be used due to Node.js flags #3025
Comments
Since the error is initiated by Line 24 in ada1a4f
I think the main process has to stop forking worker for the rest of the test files and then print appropriate error message, otherwise we will get aggregated error with same error messages. But I am afraid, by changing stopOnError to true in Line 302 in ada1a4f
Second approach: Check if the error is Line 309 in ada1a4f
warnWorkerThreadError: true property to the emitted internal-error event, so the reporter can display a warning message.
What's your opinion? |
We could also check whether worker threads are enabled (in AVA's config) and then create a worker. If that fails with a recognized error we don't run the tests at all. The worker can be created with the |
See also #3207. |
See discussion in #3015. Certain Node.js flags stop worker threads from working. We should recognize that error (
ERR_WORKER_INVALID_EXEC_ARGV
) and print a useful error message so users know to disable worker threads in AVA.The text was updated successfully, but these errors were encountered: