<!-- Thank you for reporting an issue. This issue tracker is for bugs and issues found within Node.js core. If you require more general support please file an issue on our help repo. https://github.com/nodejs/help Please fill in as much of the template below as you're able. Version: output of `node -v` Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows) Subsystem: if known, please specify affected core module name If possible, please provide code that demonstrates the problem, keeping it as simple and free of external dependencies as you are able. --> * **Version**: master * **Platform**: debain8-x86 * **Subsystem**: fs, test <!-- Enter your issue details below this comment. --> First discovered in CI run of https://github.com/nodejs/node/pull/18348, but the PR was not touching any code path covered by this test (it only changed synchronous APIs) https://ci.nodejs.org/job/node-test-commit-linux/15884/nodes=debian8-x86/console ``` not ok 545 parallel/test-fs-read-stream-err --- duration_ms: 0.135 severity: fail stack: |- ... ``` Then reproduced with master, 1 out of 100 with `--repeat 100 -J` and `RUN_TIMES=100` https://ci.nodejs.org/job/node-stress-single-test/1758/nodes=debian8-x86/console
First discovered in CI run of #18348, but the PR was not touching any code path covered by this test (it only changed synchronous APIs)
https://ci.nodejs.org/job/node-test-commit-linux/15884/nodes=debian8-x86/console
Then reproduced with master, 1 out of 100 with
--repeat 100 -JandRUN_TIMES=100https://ci.nodejs.org/job/node-stress-single-test/1758/nodes=debian8-x86/console