Repository navigation
flaky test-regress-GH-814_2 #34527
Description
Activity
- addedfsIssues and PRs related to file-system APIs and the fs module.Issues and PRs related to file-system APIs and the fs module.libuvIssues and PRs related to the libuv dependency or the uv binding.Issues and PRs related to the libuv dependency or the uv binding.flaky-testIssues and PRs involving tests that fail intermittently in CI.Issues and PRs involving tests that fail intermittently in CI.
on Jul 27, 2020 @nodejs/testing @nodejs/fs @nodejs/libuv
Looks like a copy-paste error with the
RUN_TESTSparameter for that stress run. I've corrected it and started a rebuild: https://ci.nodejs.org/job/node-stress-single-test/152/Reacted by Rich TrottThe test crashes with -9, which I believe means libuv is complaining about a bad file descriptor.
Signal 9 is
SIGKILL. Looking at the test, this is most likely due to the process running out of memory.The test crashes with -9, which I believe means libuv is complaining about a bad file descriptor.
Signal 9 is
SIGKILL. Looking at the test, this is most likely due to the process running out of memory.Yes, I'm more-than-mildly embarrassed that my brain didn't realize that a crash wouldn't be a uv error code but the signal code instead.
So if it's probably running out of memory, then I guess the thing to do might be to add a free memory check before running like we do for some other tests.
So if it's probably running out of memory, then I guess the thing to do might be to add a free memory check before running like we do for some other tests.
But not if we don't/can't replicate the problem, I guess....
PR to replace the test(s) with a more modern one: #34530
- added a commit that references this issue
on Jul 30, 2020 - added 3 commits that reference this issue
on Aug 6, 2020 - added a commit that references this issue
on May 22, 2026
What steps will reproduce the bug?
Run test/pummel/test-regress-GH-814_2.js on fedora-last-latest-x64 in CI.
How often does it reproduce? Is there a required condition?
Not every time. Running https://ci.nodejs.org/job/node-stress-single-test/151/ right now to see how often.
What is the expected behavior?
The test should pass.
What do you see instead?
The test crashes with -9, which I believe means libuv is complaining about a bad file descriptor.
Additional information
Something similar to this was going on with readstream last year and I think @addaleax fixed it. Maybe
fshas the same/similar issue, perhaps when explicitfs.close()is not used?