| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Keep the registered finalization object strongly reachable until process exit so the test does not depend on GC timing. Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com> Assisted-by: openai:gpt-5.5
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #63394 +/- ##
=======================================
Coverage 90.05% 90.05%
=======================================
Files 714 714
Lines 225656 225704 +48
Branches 42696 42717 +21
=======================================
+ Hits 203214 203267 +53
- Misses 14220 14231 +11
+ Partials 8222 8206 -16 see 49 files with indirect coverage changes 🚀 New features to boost your workflow:
|
Sorry, something went wrong.
|
Converted to draft, as the flaky test is likely fixed by #63209 The PRs for which the CI failed on https://github.com/nodejs/reliability/blob/main/reports/2026-05-15.md#jstest-failure did not contain the fix from #63209. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fixes an intermittent failure in parallel/test-process-finalization.
The different-registry-per-thread.mjs fixture registered an object with
process.finalization.register() but did not keep that object strongly
reachable until process exit. Since finalization stores weak references, GC
could collect the main-thread object before shutdown, causing the expected
shutdown on main thread output to be missing.
This keeps the registered reference reachable through the exit phase so the
test verifies per-thread finalization behavior without depending on GC timing.
Refs: https://github.com/nodejs/reliability/blob/main/reports/2026-05-15.md#jstest-failure
Assisted-by: openai:gpt-5.5