67786c1270
Previously `--test-timeout` is set on per test execution, this is obviously a bug as per test execution is hard to be expected, this patch addresses the issue by setting `timeout` from per execution to per test. This patch also fixes a minor issue that `--test-timeout` is not being respected when running without `--test`. PR-URL: https://github.com/nodejs/node/pull/57672 Fixes: https://github.com/nodejs/node/issues/57656 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Pietro Marchini <pietro.marchini94@gmail.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
21 lines
701 B
JavaScript
21 lines
701 B
JavaScript
'use strict';
|
|
const common = require('../common');
|
|
const fixtures = require('../common/fixtures');
|
|
const { strictEqual } = require('node:assert');
|
|
const { relative } = require('node:path');
|
|
const { run } = require('node:test');
|
|
const fixture = fixtures.path('test-runner', 'index.js');
|
|
const relativePath = relative(process.cwd(), fixture);
|
|
const stream = run({
|
|
files: [relativePath],
|
|
timeout: common.platformTimeout(100),
|
|
});
|
|
|
|
stream.on('test:fail', common.mustCall((result) => {
|
|
strictEqual(result.name, relativePath);
|
|
strictEqual(result.details.error.failureType, 'testCodeFailure');
|
|
strictEqual(result.line, 1);
|
|
strictEqual(result.column, 1);
|
|
strictEqual(result.file, fixture);
|
|
}));
|