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 107.170.28.213/107.170.28.213:25817' is disconnected.
at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:216)
at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:286)
at com.sun.proxy.$Proxy79.isAlive(Unknown Source)
at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1213)
at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1205)
Reason
Build timed out (after 15 minutes). Marking the build as failed.
ERROR: Build step failed with exception
java.lang.NullPointerException: no workspace from node hudson.slaves.DumbSlave[test-equinix-ubuntu2004_container-armv7l-2] which is computer hudson.slaves.SlaveComputer@2ad6001 and has channel null
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:113)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:91)
at org.jenkinsci.plugins.postbuildscript.processor.Processor.processBuildSteps(Processor.java:180)
at org.jenkinsci.plugins.postbuildscript.processor.Processor.processScripts(Processor.java:91)
Reason
ERROR: Step ?Publish JUnit test result report? failed: no workspace for ...
not ok 3330 pummel/test-http-upload-timeout
---
duration_ms: 5.726
severity: fail
exitcode: 1
stack: |-
/home/iojs/build/workspace/node-test-commit-arm/test/pummel/test-http-upload-timeout.js:34
throw new Error('Unexpected timeout');
^
Error: Unexpected timeout
at Socket.<anonymous> (/home/iojs/build/workspace/node-test-commit-arm/test/pummel/test-http-upload-timeout.js:34:11)
at Socket.emit (node:events:525:35)
at Socket._onTimeout (node:net:522:8)
at listOnTimeout (node:internal/timers:564:17)
at process.processTimers (node:internal/timers:507:7)
Node.js v19.0.0-pre
...
not ok 790 parallel/test-worker-heap-snapshot
---
duration_ms: 1.437
severity: fail
exitcode: 134
stack: |-
FATAL ERROR: HandleScope::HandleScope Entering the V8 API without proper locking in place
...
Failures in node-test-pull-request/45504 to node-test-pull-request/45598 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
Build timed out (after 15 minutes). Marking the build as failed.
Example
Build Failure
ERROR: Build step failed with exception
Example
ERROR: Step ?Publish JUnit test result report? failed: no workspace for ...
Example
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Example
undefined
Unknown
Example
JSTest Failure
pummel/test-http-upload-timeout
Example
sequential/test-gc-http-client
Example
sequential/test-gc-http-client-onerror
Example
parallel/test-worker-heap-snapshot
Example
parallel/test-heapsnapshot-near-heap-limit-worker
Example
parallel/test-vm-break-on-sigint
Example
sequential/test-gc-http-client-timeout
Example
parallel/test-fs-write-stream-file-handle
Example
parallel/test-worker-fshandles-open-close-on-termination
Example
Progress
Backing channel 'JNLP4-connect connection from ... is disconnected.
(10)Build timed out (after 15 minutes). Marking the build as failed.
(2)ERROR: Build step failed with exception
(4)ERROR: Step ?Publish JUnit test result report? failed: no workspace for ...
(4)ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
(3)Unknown
(26)pummel/test-http-upload-timeout
(19)sequential/test-gc-http-client
(7)sequential/test-gc-http-client-onerror
(7)parallel/test-worker-heap-snapshot
(6)parallel/test-heapsnapshot-near-heap-limit-worker
(3)parallel/test-vm-break-on-sigint
(3)sequential/test-gc-http-client-timeout
(3)parallel/test-fs-write-stream-file-handle
(2)parallel/test-worker-fshandles-open-close-on-termination
(2)The text was updated successfully, but these errors were encountered: