Skip to content

Commit 3738b57

Browse files
kvakilkvakil
authored
test: move tests with many workers to sequential
These tests spawn many workers, which may be CPU intensive causing timeouts (see the referenced PR for more details). Let's move them to sequential. Refs: #44090 PR-URL: #44139 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Santiago Gimeno <[email protected]>
1 parent a31d572 commit 3738b57

3 files changed

Lines changed: 1 addition & 1 deletion

File tree

test/parallel/test-worker-fshandles-error-on-termination.js renamed to test/sequential/test-worker-fshandles-error-on-termination.js

File renamed without changes.

test/parallel/test-worker-fshandles-open-close-on-termination.js renamed to test/sequential/test-worker-fshandles-open-close-on-termination.js

File renamed without changes.

test/parallel/test-worker-http2-stream-terminate.js renamed to test/sequential/test-worker-http2-stream-terminate.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ if (!common.hasCrypto)
55
const assert = require('assert');
66
const http2 = require('http2');
77
const makeDuplexPair = require('../common/duplexpair');
8-
const { Worker, parentPort } = require('worker_threads');
8+
const { parentPort, Worker } = require('worker_threads');
99

1010
// This test ensures that workers can be terminated without error while
1111
// stream activity is ongoing, in particular the C++ function

0 commit comments

Comments
 (0)