You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Improve and document the issue with test_stack_varargs* (#7951)
I found out why these fail sometimes - in node.js, we set argv[0] to the native program being run. We allocate that on the stack (I guess to avoid a malloc). And so the filename of the program being run influences how much stack we use. As a result, if a random temp dir is used with a particularly long name, we can error in tests that check for not exceeding a minimal amount of stack usage.
Amusingly, in particular this explains why I couldn't see it locally, where I run with EMTEST_SAVE_DIR - that makes it use a standard (short) test dir name, not a random one which might be long...
I doubled the amount of stack we allow in those tests (they check that loops don't increase stack space unboundedly), which should make them ok even with a path name of a few K now, and documented it to avoid future confusion should they fail again.
0 commit comments