1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

test: move tests with many workers to sequential

Browse Source 
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: https://github.com/nodejs/node/pull/44090
PR-URL: https://github.com/nodejs/node/pull/44139
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>
This commit is contained in:
Keyhan Vakil 2022-08-07 05:44:33 -07:00 committed by GitHub
parent a31d572f00
commit 3738b57102
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

0
test/parallel/test-worker-fshandles-error-on-termination.js → test/sequential/test-worker-fshandles-error-on-termination.js
View File

0
test/parallel/test-worker-fshandles-open-close-on-termination.js → test/sequential/test-worker-fshandles-open-close-on-termination.js
View File

2
test/parallel/test-worker-http2-stream-terminate.js → test/sequential/test-worker-http2-stream-terminate.js
View File

@ -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