Skip to content

tools: wait for test processes instead of polling #83627

tools: wait for test processes instead of polling

tools: wait for test processes instead of polling #83627

Triggered via push October 3, 2026 13:38
Status Failure
Total duration 1h 47m 2s
Artifacts –

test-macos.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 notice
test-macOS
Process completed with exit code 2.
test-macOS: test/benchmark/test-benchmark-http.js#L0
--- stderr --- /Users/runner/work/node/node/node/benchmark/http/is_valid_header.js:67 if (isValidHeaderName(list[i % len])) valid++; ^ TypeError: isValidHeaderName is not a function at main (/Users/runner/work/node/node/node/benchmark/http/is_valid_header.js:67:13) at /Users/runner/work/node/node/node/benchmark/common.js:64:9 at process.processTicksAndRejections (node:internal/process/task_queues:85:11) Node.js v26.10.1-pre node:internal/process/promises:322 new UnhandledPromiseRejection(reason); ^ UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "1". at throwUnhandledRejectionsMode (node:internal/process/promises:322:7) at processPromiseRejections (node:internal/process/promises:405:17) at process.processTicksAndRejections (node:internal/process/task_queues:106:37) { code: 'ERR_UNHANDLED_REJECTION' } Node.js v26.10.1-pre node:internal/assert/utils:146 throw error; ^ AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: 1 !== 0 at ChildProcess.<anonymous> (/Users/runner/work/node/node/node/test/common/benchmark.js:28:12) at ChildProcess.emit (node:events:514:20) at ChildProcess._handle.onexit (node:internal/child_process:323:12) { generatedMessage: true, code: 'ERR_ASSERTION', actual: 1, expected: 0, operator: 'strictEqual', diff: 'simple' } Node.js v26.10.1-pre Command: out/Release/node /Users/runner/work/node/node/node/test/benchmark/test-benchmark-http.js
test-macOS
Due to capacity constraints, jobs targeting macOS arm64 runners may experience longer queue times.