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]>
nodejs · Sep 5, 2022 · 5759e18 · 5759e18
1 parent e8ef169
commit 5759e18
Show file tree

Hide file tree

Showing 3 changed files with 1 addition and 1 deletion.
diff --git a/...-worker-fshandles-error-on-termination.js → ...-worker-fshandles-error-on-termination.js b/...-worker-fshandles-error-on-termination.js → ...-worker-fshandles-error-on-termination.js
diff --git a/...er-fshandles-open-close-on-termination.js → ...er-fshandles-open-close-on-termination.js b/...er-fshandles-open-close-on-termination.js → ...er-fshandles-open-close-on-termination.js
diff --git a/...lel/test-worker-http2-stream-terminate.js → ...ial/test-worker-http2-stream-terminate.js b/...lel/test-worker-http2-stream-terminate.js → ...ial/test-worker-http2-stream-terminate.js
@@ -5,7 +5,7 @@ if (!common.hasCrypto)
 const assert = require('assert');
 const http2 = require('http2');
 const makeDuplexPair = require('../common/duplexpair');
-const { Worker, parentPort } = require('worker_threads');
+const { parentPort, Worker } = require('worker_threads');
 
 // This test ensures that workers can be terminated without error while
 // stream activity is ongoing, in particular the C++ function