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 203.217.18.114/203.217.18.114:46156' is disconnected.
at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:216)
at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:285)
at com.sun.proxy.$Proxy71.isAlive(Unknown Source)
at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1147)
at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1139)
Error: Not supported
at vm:module(0):1:1
at SourceTextModule.evaluate (internal/vm/module.js:224:23)
at embedder_main_6.js:1:328
at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:705115) UnhandledPromiseRejectionWarning: Unhandled promise rejection. 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(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
not ok 1137 parallel/test-http-parser-timeout-reset
---
duration_ms: 1.312
severity: fail
exitcode: 1
stack: |-
Mismatched noop function calls. Expected exactly 3, actual 6.
at Proxy.mustCall (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd11-x64/test/common/index.js:331:10)
at Server.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd11-x64/test/parallel/test-http-parser-timeout-reset.js:37:42)
at Object.onceWrapper (events.js:420:28)
at Server.emit (events.js:314:20)
at emitListeningNT (net.js:1322:10)
at processTicksAndRejections (internal/process/task_queues.js:79:21)
...
not ok 8 wasi/test-wasi
---
duration_ms: 2.927
severity: fail
exitcode: 1
stack: |-
executing cant_dotdot
(node:90112) ExperimentalWarning: WASI is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
fd_prestat_get(3, 69720)
fd_prestat_dir_name(3, 131088, 9)
fd_prestat_get(4, 69720)
fd_prestat_dir_name(4, 131152, 5)
fd_prestat_get(5, 69720)
environ_sizes_get(69724, 69720)
environ_get(134464, 131168)
fd_fdstat_get(3, 69672)
path_open(3, 1, 1033, 14, 0, 264240830, 268435455, 0, 69668)
executing clock_getres
(node:90113) ExperimentalWarning: WASI is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
fd_prestat_get(3, 69688)
fd_prestat_dir_name(3, 131088, 9)
fd_prestat_get(4, 69688)
fd_prestat_dir_name(4, 131152, 5)
fd_prestat_get(5, 69688)
environ_siz...
not ok 116 node-api/test_worker_terminate_finalization/test
---
duration_ms: 2.144
severity: fail
exitcode: 1
stack: |-
events.js:312
throw er; // Unhandled 'error' event
^
AssertionError [ERR_ASSERTION]: function should not have been called at /home/iojs/build/workspace/node-test-binary-arm/test/node-api/test_worker_terminate_finalization/test.js:7
called with arguments: [Error: Invalid argument]
at Worker.mustNotCall (/home/iojs/build/workspace/node-test-binary-arm/test/common/index.js:425:12)
at Worker.emit (events.js:343:20)
at Worker.[kOnErrorMessage] (internal/worker.js:241:10)
at Worker.[kOnMessage] (internal/worker.js:251:37)
at MessagePort.<anonymous> (internal/worker.js:167:57)
at MessagePort.[nodejs.internal.kHybridDispatch] (internal/event_target.js:352:41)
at MessagePort.exports.emitMessage (internal/per_context/messageport.js:18:26)
Emitted 'error' event on process instance at:
at e...
not ok 2469 parallel/test-worker-init-failure
---
duration_ms: 2.469
severity: fail
exitcode: 1
stack: |-
child stdout:
child stderr: events.js:291
throw er; // Unhandled 'error' event
^
AssertionError [ERR_ASSERTION]: The input did not match the regular expression /EMFILE/. Input:
'ENOENT: no such file or directory, uv_cwd'
at Worker.<anonymous> (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/test/parallel/test-worker-init-failure.js:38:14)
at Worker.emit (events.js:314:20)
at Worker.[kOnErrorMessage] (internal/worker.js:241:10)
at Worker.[kOnMessage] (internal/worker.js:251:37)
at MessagePort.<anonymous> (internal/worker.js:167:57)
at MessagePort.[nodejs.internal.kHybridDispatch] (internal/event_target.js:352:41)
at MessagePort.exports.emitMessage (internal/per_context/messageport.js:18:26)
at Worker.[kOnExit] (internal/worker.js:223:5)
at Worker.<compute...
Progress
Backing channel 'JNLP4-connect connection from ... is disconnected. (3)
fatal error: ld terminated with signal 9 [Killed] (3)
Failures in node-test-pull-request/32593 to node-test-pull-request/32686 that failed more than 2 PRs
(Generated with
ncu-ci walk pr --stats=true --markdown /home/runner/work/nodejs-reliability/nodejs-reliability/results.md
)Jenkins Failure
Backing channel 'JNLP4-connect connection from ... is disconnected.
Example
Git Failure
Build Failure
fatal error: ld terminated with signal 9 [Killed]
Example
Error: Not supported
Example
Failed to trigger node-test-commit
Example
JSTest Failure
parallel/test-http-parser-timeout-reset
Example
wasi/test-wasi
Example
parallel/test-http-destroyed-socket-write2
Example
parallel/test-repl
Example
node-api/test_worker_terminate_finalization/test
Example
parallel/test-async-hooks-http-parser-destroy
Example
parallel/test-fs-utimes
Example
parallel/test-worker-init-failure
Example
Progress
Backing channel 'JNLP4-connect connection from ... is disconnected.
(3)fatal error: ld terminated with signal 9 [Killed]
(3)Error: Not supported
(2)Failed to trigger node-test-commit
(2)parallel/test-http-parser-timeout-reset
(6)wasi/test-wasi
(4)parallel/test-http-destroyed-socket-write2
(3)parallel/test-repl
(3)node-api/test_worker_terminate_finalization/test
(2)parallel/test-async-hooks-http-parser-destroy
(2)parallel/test-fs-utimes
(2)parallel/test-worker-init-failure
(2)The text was updated successfully, but these errors were encountered: