You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
not ok 480 parallel/test-child-process-exec-timeout-kill
---
duration_ms: 0.112
severity: fail
exitcode: 1
stack: |-
[stdout]
[stderr] /home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-child-process-exec-timeout-kill.js:17
logInTimeout(kExpiringChildRunTime);
^
TypeError: logInTimeout is not a function
at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-child-process-exec-timeout-kill.js:17:3)
at Module._compile (node:internal/modules/cjs/loader:1198:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1252:10)
at Module.load (node:internal/modules/cjs/loader:1076:32)
at Function.Module._load (node:internal/modules/cjs/loader:911:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
at node:internal/main/run_main_module:22:47
node:assert:124
throw new AssertionError(obj);
^
...
not ok 941 sequential/test-worker-prof
---
duration_ms: 30228.28300
severity: fail
exitcode: 1
stack: |-
node:assert:125
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: child exited with signal: {
error: Error: spawnSync C:\workspace\node-test-binary-windows-js-suites\node\Release\node.exe ETIMEDOUT
at Object.spawnSync (node:internal/child_process:1124:20)
at spawnSync (node:child_process:876:24)
at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\sequential\test-worker-prof.js:52:23)
at Module._compile (node:internal/modules/cjs/loader:1241:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
at Module.load (node:internal/modules/cjs/loader:1091:32)
at Module._load (node:internal/modules/cjs/loader:938:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
at node:internal/main/ru...
not ok 852 parallel/test-worker-memory
---
duration_ms: 1443.99600
severity: fail
exitcode: 3221226356
stack: |-
run() called with n=7.5 (numWorkers=8)
run() called with n=7.5 (numWorkers=8)
run() called with n=7.5 (numWorkers=8)
run() called with n=7.5 (numWorkers=8)
run() called with n=7.5 (numWorkers=8)
run() called with n=7.5 (numWorkers=8)
run() called with n=7.5 (numWorkers=8)
run() called with n=7.5 (numWorkers=8)
run() called with n=6.5 (numWorkers=8)
run() called with n=6.5 (numWorkers=8)
run() called with n=6.5 (numWorkers=8)
run() called with n=6.5 (numWorkers=8)
run() called with n=6.5 (numWorkers=8)
run() called with n=6.5 (numWorkers=8)
run() called with n=6.5 (numWorkers=8)
run() called with n=6.5 (numWorkers=8)
run() called with n=5.5 (numWorkers=8)
run() called with n=5.5 (numWorkers=8)
run() called with n=5.5 (numWorkers=8)
run() called with n=5.5 (numWorkers=8)
run() called with n=5.5 (numWorkers=8...
not ok 1499 parallel/test-http-server-consumed-timeout
---
duration_ms: 1.342
severity: fail
exitcode: 1
stack: |-
node:assert:171
throw err;
^
AssertionError [ERR_ASSERTION]: Request timeout should not fire
at IncomingMessage.<anonymous> (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-http-server-consumed-timeout.js:51:14)
at IncomingMessage.emit (node:events:513:28)
at Socket.socketOnTimeout (node:_http_server:624:50)
at Socket.emit (node:events:513:28)
at Socket._onTimeout (node:net:550:8)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7) {
generatedMessage: false,
code: 'ERR_ASSERTION',
actual: undefined,
expected: undefined,
operator: 'fail'
}
...
not ok 1827 parallel/test-inspector-break-when-eval
---
duration_ms: 15617.55500
severity: fail
exitcode: 1
stack: |-
[test] Connecting to a child Node process
[test] Testing /json/list
[err] Debugger listening on ws://127.0.0.1:38537/ef948993-2de7-4904-8d9e-a330913a6852
[err] For help, see: https://nodejs.org/en/docs/inspector
[err]
[test] Setting up a debugger
[err] Debugger attached.
[err]
Timed out waiting for matching notification (Initial pause)
1
...
not ok 3607 parallel/test-runner-inspect
---
duration_ms: 120068.88900
severity: fail
exitcode: -15
stack: |-
timeout
[test] Connecting to a child Node process
[test] Testing /json/list
[err] (node:2699187) Warning: Using the inspector with --test forces running at a concurrency of 1. Use the inspectPort option to run with concurrency
[err] (Use `node --trace-warnings ...` to show where the warning was created)
[err]
[out] TAP version 13
[out]
[err] Debugger listening on ws://127.0.0.1:40709/388ce237-645b-46c3-8e50-4195aa09025b
[err] For help, see: https://nodejs.org/en/docs/inspector
[err]
[err] Debugger attached.
[err]
[err] For help, see: https://nodejs.org/en/docs/inspector
[err]
[out] # Debugger ending on ws://127.0.0.1:40709/388ce237-645b-46c3-8e50-4195aa09025b
[out]
...
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository
fatal: Could not read from remote repository.
fatal: failed to run repack
Reason
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Failures in node-test-pull-request/53461 to node-test-pull-request/53558 that failed 2 or more PRs
(Generated with
ncu-ci walk pr --stats=true --markdown /home/runner/work/reliability/reliability/results.md)JSTest Failure
parallel/test-child-process-exec-timeout-killExample
sequential/test-cpu-prof-killExample
sequential/test-http-regr-gh-2928Example
sequential/test-worker-profExample
parallel/test-crypto-dhExample
parallel/test-tls-ticket-clusterExample
parallel/test-worker-memoryExample
sequential/test-perf-hooksExample
parallel/test-fs-watch-recursive-add-fileExample
parallel/test-fs-watch-recursive-add-file-to-existing-subfolderExample
parallel/test-fs-watch-recursive-add-file-to-new-folderExample
parallel/test-fs-watch-recursive-add-file-with-urlExample
parallel/test-fs-watch-recursive-symlinkExample
parallel/test-http-server-consumed-timeoutExample
parallel/test-inspector-break-when-evalExample
parallel/test-runner-inspectExample
pummel/test-heapdump-shadow-realmExample
sequential/test-single-executable-application-snapshotExample
Jenkins Failure
Build timed out (after 60 minutes). Marking the build as failed.Example
CCTest Failure
C:\workspace\node-compile-windows\node\test\cctest\test_inspector_socket.cc(323): error: Value of: (!expectation.read_expected)Example
Git Failure
Build Failure
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repositoryExample
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?Example
Failed to trigger fanned buildExample
ERROR: No files found with the specified search criteria.Example
fatal: No rebase in progress?Example
Progress
parallel/test-child-process-exec-timeout-kill(5)sequential/test-cpu-prof-kill(5)sequential/test-http-regr-gh-2928(4)sequential/test-worker-prof(4)parallel/test-crypto-dh(3)parallel/test-tls-ticket-cluster(3)parallel/test-worker-memory(3)sequential/test-perf-hooks(3)parallel/test-fs-watch-recursive-add-file(2)parallel/test-fs-watch-recursive-add-file-to-existing-subfolder(2)parallel/test-fs-watch-recursive-add-file-to-new-folder(2)parallel/test-fs-watch-recursive-add-file-with-url(2)parallel/test-fs-watch-recursive-symlink(2)parallel/test-http-server-consumed-timeout(2)parallel/test-inspector-break-when-eval(2)parallel/test-runner-inspect(2)pummel/test-heapdump-shadow-realm(2)sequential/test-single-executable-application-snapshot(2)Build timed out (after 60 minutes). Marking the build as failed.(10)C:\workspace\node-compile-windows\node\test\cctest\test_inspector_socket.cc(323): error: Value of: (!expectation.read_expected)(2)fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository(6)ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(4)Failed to trigger fanned build(3)ERROR: No files found with the specified search criteria.(2)fatal: No rebase in progress?(2)The text was updated successfully, but these errors were encountered: