mirror of
https://github.com/nodejs/node.git
synced 2024-11-21 10:59:27 +00:00
bae14b7914
Our CI already run test files in parallel, having `node:test` spawns child processes concurrently could lead to oversubscribing the CI machine. This commit sets the `concurrency` depending on the presence of `TEST_PARALLEL` in the env, so running the test file individually still spawns child processes concurrently, and running the whole test suite does not oversubscribe the machine. PR-URL: https://github.com/nodejs/node/pull/52177 Reviewed-By: Vinícius Lourenço Claro Cardoso <contact@viniciusl.com.br> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
29 lines
734 B
JavaScript
29 lines
734 B
JavaScript
'use strict';
|
|
|
|
const { mustCall } = require('../common');
|
|
const fixtures = require('../common/fixtures');
|
|
const assert = require('node:assert');
|
|
const { spawn } = require('node:child_process');
|
|
const { execPath } = require('node:process');
|
|
const { describe, it } = require('node:test');
|
|
|
|
|
|
describe('ESM: REPL runs', { concurrency: !process.env.TEST_PARALLEL }, () => {
|
|
it((t, done) => {
|
|
const child = spawn(execPath, [
|
|
'--interactive',
|
|
], {
|
|
cwd: fixtures.path('es-modules', 'pkgimports'),
|
|
});
|
|
|
|
child.stdin.end(
|
|
'try{require("#test");await import("#test")}catch{process.exit(-1)}'
|
|
);
|
|
|
|
child.on('exit', mustCall((code) => {
|
|
assert.strictEqual(code, 0);
|
|
done();
|
|
}));
|
|
});
|
|
});
|