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
java.io.IOException: Backing channel 'JNLP4-connect connection from p8-aix2-nodejs03.osuosl.org/140.211.9.131:48561' is disconnected.
at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:216)
at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:286)
at com.sun.proxy.$Proxy82.isAlive(Unknown Source)
at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1213)
at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1205)
Git Failure
Build Failure
Reason
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE
Reason
ERROR: Step ?Publish JUnit test result report? failed: no workspace for ...
not ok 327 parallel/test-common-expect-warning
---
duration_ms: 0.812
severity: fail
exitcode: 1
stack: |-
node:assert:1026
throw err;
^
AssertionError [ERR_ASSERTION]: The input did not match the regular expression /Unexpected extra warning received/. Input:
''
at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-arm-debug/test/parallel/test-common-expect-warning.js:41:14)
at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-arm-debug/test/common/index.js:401:15)
at ChildProcess.emit (node:events:522:28)
at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: '',
expected: /Unexpected extra warning received/,
operator: 'match'
}
Node.js v18.0.0-pre
...
not ok 703 parallel/test-vm-timeout-escape-promise-2
---
duration_ms: 0.250
severity: fail
exitcode: 1
stack: |-
C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-vm-timeout-escape-promise-2.js:20
throw new Error(
^
Error: escaped timeout at 100 milliseconds!
at loop (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-vm-timeout-escape-promise-2.js:20:13)
at evalmachine.<anonymous>:1:30
at Script.runInContext (node:vm:139:12)
at Script.runInNewContext (node:vm:144:17)
at Object.runInNewContext (node:vm:298:38)
at assert.throws.code (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-vm-timeout-escape-promise-2.js:27:6)
at getActual (node:assert:757:5)
at Function.throws (node:assert:903:24)
at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-vm-timeout-escape-promise-2.js:26:8)
...
not ok 1565 parallel/test-inspector-multisession-ws
---
duration_ms: 15.484
severity: fail
exitcode: 1
stack: |-
[test] Connecting to a child Node process
[test] Testing /json/list
[test] Connecting to a child Node process
[test] Testing /json/list
[err] Debugger listening on ws://127.0.0.1:57202/0ebf63ca-44c3-4eab-a923-e8cf9d6ec742
[err] For help, see: https://nodejs.org/en/docs/inspector
[err]
[err] Debugger attached.
[err] Debugger attached.
[err]
[test] Breaking in code and verifying events are fired
Timed out waiting for matching notification (Initial pause)
1
...
not ok 754 parallel/test-windows-failed-heap-allocation
---
duration_ms: 1.725
severity: fail
exitcode: 1
stack: |-
<--- Last few GCs --->
[8412:0000015ECFDE8D30] 20 ms: Mark-sweep 2.6 (4.9) -> 2.5 (4.9) MB, 2.5 / 0.0 ms (average mu = 0.652, current mu = 0.652) allocation failure GC in old space requested
[8412:0000015ECFDE8D30] 26 ms: Mark-sweep 2.8 (5.1) -> 2.8 (5.4) MB, 3.7 / 0.0 ms (average mu = 0.525, current mu = 0.374) allocation failure GC in old space requested
<--- JS stacktrace --->
#
# Fatal javascript OOM in Reached heap limit
#
node:assert:123
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Wrong exit code of 2147483651! Expected 134 for abort
at C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-windows-failed-heap-allocation.js:29:10
at C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:401:15
...
not ok 844 sequential/test-worker-prof
---
duration_ms: 30.293
severity: fail
exitcode: 1
stack: |-
node:assert:123
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:1109:20)
at spawnSync (node:child_process:803:24)
at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\sequential\test-worker-prof.js:53:23)
at Module._compile (node:internal/modules/cjs/loader:1097:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1149:10)
at Module.load (node:internal/modules/cjs/loader:975:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
at node:intern...
Progress
Backing channel 'JNLP4-connect connection from ... is disconnected. (3)
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (3)
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
ERROR: Step ?Publish JUnit test result report? failed: no workspace for ... (2)
Failures in node-test-pull-request/42126 to node-test-pull-request/42225 that failed more than 2 PRs
(Generated with
ncu-ci walk pr --stats=true --markdown /home/runner/work/reliability/reliability/results.md)Jenkins Failure
Backing channel 'JNLP4-connect connection from ... is disconnected.Example
Git Failure
Build Failure
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?Example
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?Example
ERROR: Step ?Publish JUnit test result report? failed: no workspace for ...Example
Failed to trigger node-test-commitExample
JSTest Failure
parallel/test-fs-rmdir-recursiveExample
parallel/test-crypto-secure-heapExample
node-api/test_fatal/test_threads_reportExample
parallel/test-common-expect-warningExample
node-api/test_fatal/test_threadsExample
parallel/test-crypto-dhExample
parallel/test-crypto-dh-constructorExample
parallel/test-fs-rmExample
parallel/test-vm-timeout-escape-promise-2Example
sequential/test-cpu-prof-worker-argvExample
parallel/test-child-process-fork-closed-channel-segfaultExample
parallel/test-child-process-pipe-dataflowExample
parallel/test-crypto-dh-leakExample
parallel/test-crypto-dh-odd-keyExample
parallel/test-finalization-group-regular-gcExample
parallel/test-inspector-multisession-wsExample
parallel/test-tls-ticket-clusterExample
parallel/test-trace-events-fs-syncExample
parallel/test-windows-failed-heap-allocationExample
sequential/test-worker-profExample
Progress
Backing channel 'JNLP4-connect connection from ... is disconnected.(3)ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?(3)ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2)ERROR: Step ?Publish JUnit test result report? failed: no workspace for ...(2)Failed to trigger node-test-commit(2)parallel/test-fs-rmdir-recursive(9)parallel/test-crypto-secure-heap(5)node-api/test_fatal/test_threads_report(4)parallel/test-common-expect-warning(4)node-api/test_fatal/test_threads(3)parallel/test-crypto-dh(3)parallel/test-crypto-dh-constructor(3)parallel/test-fs-rm(3)parallel/test-vm-timeout-escape-promise-2(3)sequential/test-cpu-prof-worker-argv(3)parallel/test-child-process-fork-closed-channel-segfault(2)parallel/test-child-process-pipe-dataflow(2)parallel/test-crypto-dh-leak(2)parallel/test-crypto-dh-odd-key(2)parallel/test-finalization-group-regular-gc(2)parallel/test-inspector-multisession-ws(2)parallel/test-tls-ticket-cluster(2)parallel/test-trace-events-fs-sync(2)parallel/test-windows-failed-heap-allocation(2)sequential/test-worker-prof(2)The text was updated successfully, but these errors were encountered: