René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Race condition in test-fs-read-stream-fd-leak.js","articleBody":"https://github.com/nodejs/node/blob/master/test/parallel/test-fs-read-stream-fd-leak.js\n\nThe intermittent assertion failure could be fired as follows:\nassert.js:89\n  throw new assert.AssertionError({\n  ^\nAssertionError: no leaked file descriptors using destroy() (got 5)\n    at null._onTimeout (/sandbox/johnyan/github-node/test/parallel/test-fs-read-stream-fd-leak.js:37:16)\n    at Timer.listOnTimeout (timers.js:89:15)\n\nThe race condition is spotted in the following code:\n\n``` javascript\n    if (++i === loopCount) {\n      clearTimeout(this);\n      setTimeout(function() {\n        assert.equal(0, openCount, 'no leaked file descriptors using ' +\n                     endFn + '() (got ' + openCount + ')');\n        openCount = 0;\n        callback \u0026\u0026 setTimeout(callback, 100);\n      }, 100);\n    }\n```\n\nIn the failing case, the first setTimeout function is fired before all streams are properly closed. If reduce the setTimeout period (say from 100 to 1), the failure rate is increased. Depends on the running environment (slow/fast), the failure rate varies. Can anyone suggest a better solution to this?\n","author":{"url":"https://github.com/john-yan","@type":"Person","name":"john-yan"},"datePublished":"2015-10-06T15:19:21.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/3215/node/issues/3215"}