mirror of
https://github.com/nodejs/node.git
synced 2024-12-01 16:10:02 +01:00
9fa94237c8
Timer-dependent tests fail frequently on certain platforms in CI when run in parallel with other tests, likely due to competition for resources. Move test-repl-timeout-throw to sequential to avoid this problem. Also did some minor refactoring (var->const and more use of assert.strictEqual of looser assertions). PR-URL: https://github.com/nodejs/node/pull/9431 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Johan Bergstrom <bugs@bergstroem.nu> |
||
---|---|---|
.. | ||
sequential.status | ||
test-child-process-emfile.js | ||
test-child-process-execsync.js | ||
test-child-process-fork-getconnections.js | ||
test-child-process-pass-fd.js | ||
test-crypto-timing-safe-equal.js | ||
test-debug-host-port.js | ||
test-debugger-debug-brk.js | ||
test-deprecation-flags.js | ||
test-dgram-pingpong.js | ||
test-fs-watch.js | ||
test-http-client-timeout-with-data.js | ||
test-http-regr-gh-2928.js | ||
test-http-server-consumed-timeout.js | ||
test-init.js | ||
test-module-loading.js | ||
test-net-GH-5504.js | ||
test-net-server-address.js | ||
test-next-tick-error-spin.js | ||
test-pipe.js | ||
test-process-warnings.js | ||
test-regress-GH-784.js | ||
test-regress-GH-877.js | ||
test-regress-GH-1697.js | ||
test-regress-GH-1726.js | ||
test-regress-GH-4015.js | ||
test-regress-GH-4027.js | ||
test-repl-timeout-throw.js | ||
test-require-cache-without-stat.js | ||
test-stream2-fs.js | ||
test-stream2-stderr-sync.js | ||
test-timers-blocking-callback.js | ||
test-timers-same-timeout-wrong-list-deleted.js | ||
test-util-debug.js | ||
test-vm-timeout-rethrow.js | ||
testcfg.py |