-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
[jest-worker] Don't pass explicit env
to new Worker
when using worker_threads
#12141
Conversation
…LIZE` with `worker_threads`
Codecov Report
@@ Coverage Diff @@
## main #12141 +/- ##
=======================================
Coverage 67.71% 67.71%
=======================================
Files 328 328
Lines 16990 16991 +1
Branches 4817 4817
=======================================
+ Hits 11505 11506 +1
Misses 5452 5452
Partials 33 33
Continue to review full report at Codecov.
|
packages/jest-worker/src/workers/__tests__/NodeThreadsWorker.test.js
Outdated
Show resolved
Hide resolved
packages/jest-worker/src/workers/__tests__/NodeThreadsWorker.test.js
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks!
Thanks! |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
#12128 wasn't enough to fix the regression introduced by #12069: it was still broken when using the
NODE_OPTIONS
env var because of nodejs/node#41103 (comment).Test plan
I updated the existing tests, but I would have loved if they were not all mock-based but spawned real workers 😅