parallel/test-fs-read-stream-concurrent-reads is flaky

[joyeecheung]

Reason	parallel/test-fs-read-stream-concurrent-reads
Type	JS_TEST_FAILURE
Failed PR	3 (https://github.com/nodejs/node/pull/51687/, https://github.com/nodejs/node/pull/51810/, https://github.com/nodejs/node/pull/51623/)
Appeared	test-digitalocean-fedora38-x64-2, test-digitalocean-fedora38-x64-1, test-osuosl-debian11_container-armv7l-1
First CI	https://ci.nodejs.org/job/node-test-pull-request/57233/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/57292/

Example

not ok 1433 parallel/test-fs-read-stream-concurrent-reads
  ---
  duration_ms: 120105.09600
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

Refs: nodejs/reliability#791

[mhdawson]

Again - https://ci.nodejs.org/job/node-test-commit-linux-containered/nodes=ubuntu2204_sharedlibs_withoutssl_x64/42216/

[targos]

It's still very flaky: nodejs/reliability#835

[mhdawson]

Again - https://ci.nodejs.org/job/node-test-commit-linux/nodes=fedora-latest-x64/57391/

[jasnell]

@addaleax @gireeshpunathil ... do either of you remember why test-fs-read-stream-concurrent-reads.js was written to require 2000 streams? Based on the test it's not clear that so many iterations are required and the test is flaky. I'm think we either should reduce the number of iterations or maybe move the test to sequential --- I'm wondering if the concurrent reads and allocations may be causing the timeout errors.

[github-actions]

This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.