Repository navigation
test: disable Maglev in near-heap-limit worker test - #63398
Merged
nodejs-github-bot merged 1 commit intoMay 20, 2026
Merged
nodejs-github-bot merged 1 commit into
nodejs-github-bot merged 1 commit into
Conversation
The test expects the worker to run out of memory during startup while creating the message port. With Maglev enabled, the tiny worker heap can be exhausted earlier while generating deoptimization data, which changes the failure mode. Disable Maglev so the induced OOM reaches the path covered by the test. 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. Additional details and impacted files@@ Coverage Diff @@
## main #63398 +/- ##
==========================================
+ Coverage 90.05% 90.06% +0.01%
==========================================
Files 714 714
Lines 225704 225704
Branches 42714 42726 +12
==========================================
+ Hits 203250 203291 +41
+ Misses 14225 14189 -36
+ Partials 8229 8224 -5 🚀 New features to boost your workflow:
|
This fixes a flaky failure in
test-worker-nearheaplimit-deadlockwhere theworker's intentionally tiny heap can be exhausted by Maglev compilation before
the test reaches the worker startup path it is meant to cover.
The test already disables snapshots because snapshot deserialization can hit
OOM too early. This applies the same idea to Maglev: disable it so the induced
OOM occurs during message port creation and is reported as
ERR_WORKER_OUT_OF_MEMORY.Refs:
Assisted-by: openai:gpt-5.5