-
-
Notifications
You must be signed in to change notification settings - Fork 33.9k
test: fix embedtest in debug windows #60806
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
base: main
Are you sure you want to change the base?
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #60806 +/- ##
==========================================
+ Coverage 88.43% 88.53% +0.09%
==========================================
Files 703 703
Lines 208235 208254 +19
Branches 40085 40157 +72
==========================================
+ Hits 184162 184379 +217
+ Misses 16069 15889 -180
+ Partials 8004 7986 -18 🚀 New features to boost your workflow:
|
Failed to start CI⚠ No approving reviews found ✘ Refusing to run CI on potentially unsafe PRhttps://github.com/nodejs/node/actions/runs/19641554149 |
|
I believe this is not a windows only issue. The reason that the debug embed test did not fail on other platforms is that Line 296 in bfc729c
it didn't run embed test with debug build of node: this |
When we run the embedding tests compiled for Windows debug it crashes with the error that you can see below.
The crash happens when the code tries to create a snapshot that causes a GC run.
At that moment the
v8::Isolateis not locked to our thread and as a result debug-only V8 check causes the crash.This PR extends the scope for the Isolate-to-thread lock so all snapshot operations have the valid thread association.
I am not 100% sure that this is the best fix here. Feel free to advise on a better approach.
E.g. we can have a separate Isolate lock for the snapshot operations instead of extending the existing scope.
This PR and and PR #60807 finally unblock the test runs on Windows while working on the code.
The error log being addressed by this PR: