From 41f1e25dbc28d3d7e59f2fbd2b658db5379c7a5c Mon Sep 17 00:00:00 2001 From: zhangzifa Date: Thu, 19 Oct 2017 17:06:34 +0800 Subject: [PATCH] test: update test-timers-block-eventloop.js When CPU is busy, the above sequential case fails occasionally, expand the timeout value to fix it. Fixes: https://github.com/nodejs/node/issues/16310 --- test/sequential/test-timers-block-eventloop.js | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/test/sequential/test-timers-block-eventloop.js b/test/sequential/test-timers-block-eventloop.js index 210cf0d80a1127..f3aedc9c0c79f1 100644 --- a/test/sequential/test-timers-block-eventloop.js +++ b/test/sequential/test-timers-block-eventloop.js @@ -2,21 +2,23 @@ const common = require('../common'); const fs = require('fs'); +const commonTimeout = common.platformTimeout; const t1 = setInterval(() => { - common.busyLoop(12); -}, 10); + common.busyLoop(commonTimeout(12)); +}, common.platformTimeout(10)); const t2 = setInterval(() => { - common.busyLoop(15); -}, 10); + common.busyLoop(commonTimeout(15)); +}, commonTimeout(10)); -const t3 = setTimeout(common.mustNotCall('eventloop blocked!'), 100); +const t3 = + setTimeout(common.mustNotCall('eventloop blocked!'), commonTimeout(200)); setTimeout(function() { - fs.stat('./nonexistent.txt', (err, stats) => { + fs.stat('/dev/nonexistent', (err, stats) => { clearInterval(t1); clearInterval(t2); clearTimeout(t3); }); -}, 50); +}, commonTimeout(50));