Skip to content

test: deflake test-worker-stack-overflow-stack-size in the Node.js suite - #53062

Merged
MarshallOfSound merged 1 commit into
mainfrom
test/deflake-worker-stack-size-node-test
Aug 21, 2026
Merged

MarshallOfSound merged 1 commit into
mainfrom
test/deflake-worker-stack-size-node-test

Conversation

@MarshallOfSound

Copy link
Copy Markdown
Member

Description of Change

  • Backports test: remove impact of tier-up changes in worker stack size test nodejs/node#64271 as a patches/node patch. parallel/test-worker-stack-overflow-stack-size compares the recursion depth two Workers reach before overflowing; depth also depends on frame size, which changes if the recursive function tiers up mid-recursion, so on a loaded runner the two depths land >10% apart (e.g. w1stack = 62263, w2stack = 82360 are too far apart in this nn-test run). The upstream fix pins the function to the interpreter with %NeverOptimizeFunction.
  • The fix only shipped in Node 26.6.0+; every active branch is on 24.18.x, hence the patch + backport labels. It drops out at the next Node roll that includes it.
  • Locally under CPU load: unpatched failed 2/30 with the same assertion, patched passed 30/30.

Checklist

  • PR description included

Release Notes

Notes: none

Backports nodejs/node#64271. The test compares the recursion depth two
Workers reach before overflowing, but depth also depends on frame size,
which changes when the recursive function tiers up mid-recursion. On a
busy CI runner that lands non-deterministically and the depths end up
>10% apart. Pin the function to the interpreter so the depth is stable.

The fix is only in Node 26.6.0+, so it is carried as a patch until the
Node roll picks it up.
@MarshallOfSound
MarshallOfSound requested a review from a team as a code owner August 21, 2026 06:40
@MarshallOfSound MarshallOfSound added semver/none target/41-x-y PR should also be added to the "41-x-y" branch. target/42-x-y PR should also be added to the "42-x-y" branch. target/43-x-y PR should also be added to the "43-x-y" branch. target/44-x-y PR should also be added to the "44-x-y" branch. labels Aug 21, 2026
@MarshallOfSound
MarshallOfSound enabled auto-merge (squash) August 21, 2026 06:44
@MarshallOfSound
MarshallOfSound merged commit f9752f3 into main Aug 21, 2026
104 of 107 checks passed
@release-clerk

release-clerk Bot commented Aug 21, 2026

Copy link
Copy Markdown

No Release Notes

@trop

trop Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

I have automatically backported this PR to "41-x-y", please check out #53075

@trop

trop Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

I have automatically backported this PR to "42-x-y", please check out #53076

@trop

trop Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

I have automatically backported this PR to "44-x-y", please check out #53077

@trop trop Bot added in-flight/42-x-y and removed target/41-x-y PR should also be added to the "41-x-y" branch. labels Aug 21, 2026
@trop

trop Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

I have automatically backported this PR to "43-x-y", please check out #53078

@trop trop Bot added in-flight/44-x-y in-flight/43-x-y and removed target/42-x-y PR should also be added to the "42-x-y" branch. target/44-x-y PR should also be added to the "44-x-y" branch. labels Aug 21, 2026
@trop trop Bot added merged/41-x-y PR was merged to the "41-x-y" branch. merged/42-x-y PR was merged to the "42-x-y" branch. merged/44-x-y PR was merged to the "44-x-y" branch. merged/43-x-y PR was merged to the "43-x-y" branch. and removed target/43-x-y PR should also be added to the "43-x-y" branch. in-flight/41-x-y in-flight/42-x-y in-flight/44-x-y in-flight/43-x-y labels Aug 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

45-x-y merged/41-x-y PR was merged to the "41-x-y" branch. merged/42-x-y PR was merged to the "42-x-y" branch. merged/43-x-y PR was merged to the "43-x-y" branch. merged/44-x-y PR was merged to the "44-x-y" branch. semver/none

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

3 participants