-
-
Notifications
You must be signed in to change notification settings - Fork 33.9k
Closed
Labels
flaky-testIssues and PRs related to the tests with unstable failures on the CI.Issues and PRs related to the tests with unstable failures on the CI.fsIssues and PRs related to the fs subsystem / file system.Issues and PRs related to the fs subsystem / file system.libuvIssues and PRs related to the libuv dependency or the uv binding.Issues and PRs related to the libuv dependency or the uv binding.
Description
- Version: 15.0.0-pre (current master branch)
- Platform: fedora-last-latest-x64
- Subsystem: test, fs, libuv
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.
21:31:32 not ok 2805 pummel/test-regress-GH-814_2
21:31:32 ---
21:31:32 duration_ms: 11.27
21:31:32 severity: crashed
21:31:32 exitcode: -9
21:31:32 stack: |-
21:31:32 /home/iojs/node-tmp/.tmp.2804/GH-814_test.txt
21:31:32
21:31:32 ...
Additional information
Something similar to this was going on with readstream last year and I think @addaleax fixed it. Maybe fs has the same/similar issue, perhaps when explicit fs.close() is not used?
Metadata
Metadata
Assignees
Labels
flaky-testIssues and PRs related to the tests with unstable failures on the CI.Issues and PRs related to the tests with unstable failures on the CI.fsIssues and PRs related to the fs subsystem / file system.Issues and PRs related to the fs subsystem / file system.libuvIssues and PRs related to the libuv dependency or the uv binding.Issues and PRs related to the libuv dependency or the uv binding.