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 139.178.85.13/139.178.85.13:59368' 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 30 minutes). Marking the build as failed.
not ok 296 parallel/test-fs-rmdir-recursive
---
duration_ms: 241.250
severity: fail
exitcode: -15
stack: |-
timeout
(node:25791) [DEP0147] DeprecationWarning: In future versions of Node.js, fs.rmdir(path, { recursive: true }) will be removed. Use fs.rm(path, { recursive: true }) instead
(Use `node --trace-deprecation ...` to show where the warning was created)
...
not ok 468 parallel/test-net-connect-memleak
---
duration_ms: 0.249
severity: fail
exitcode: 1
stack: |-
Mismatched noop function calls. Expected exactly 1, actual 0.
at Proxy.mustCall (C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:375:10)
at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-net-connect-memleak.js:33:40)
at Module._compile (node:internal/modules/cjs/loader:1097:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1151: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:internal/main/run_main_module:17:47
...
not ok 320 parallel/test-common-expect-warning
---
duration_ms: 0.321
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/test/parallel/test-common-expect-warning.js:41:14)
at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-arm/test/common/index.js:417:15)
at ChildProcess.emit (node:events:527: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 274 parallel/test-fs-write-stream-file-handle
---
duration_ms: 45.493
severity: fail
exitcode: 1
stack: |-
Can't clean tmpdir: /home/iojs/tmp/.tmp.273
Files blocking: [ '.nfs0000000000000ce300006803' ]
Note: ".nfs*" might be files that were open and unlinked but not closed.
See http://nfs.sourceforge.net/#faq_d2 for details.
node:assert:123
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
+ actual - expected
+ ''
- 'hello world'
at WriteStream.<anonymous> (/home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-write-stream-file-handle.js:19:12)
at WriteStream.<anonymous> (/home/iojs/build/workspace/node-test-binary-arm/test/common/index.js:417:15)
at WriteStream.emit (node:events:527:28)
at emitCloseNT (node:internal/streams/destroy:145:10)
at processTicksAndRejections (node:internal/process/task_queues:81:21) {
gener...
@nodejs-github-bot While "multiple PRs failed on this reason" might be a somewhat useful signal, it's also relatively noisy...how about noting that the failure was happening on the base branch that the PR was trying to merge into, thus making the CI run not a good measure of whether the PR introduced a new issue?
It would also be nice to have a button for even non-collaborators to re-run a CI job suffering from unreliability issues even when run on the base branch (usually master/main).
Failures in node-test-pull-request/42605 to node-test-pull-request/42701 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 30 minutes). Marking the build as failed.
Example
Build timed out (after 15 minutes). Marking the build as failed.
Example
Build Failure
ERROR: Step ?Publish JUnit test result report? failed: no workspace for ...
Example
JSTest Failure
parallel/test-module-readonly
Example
parallel/test-crypto-dh-leak
Example
sequential/test-cpu-prof-worker-argv
Example
parallel/test-child-process-fork-closed-channel-segfault
Example
parallel/test-fs-rmdir-recursive
Example
parallel/test-http-header-overflow
Example
parallel/test-net-connect-memleak
Example
sequential/test-cpu-prof-name
Example
node-api/test_threadsafe_function/test
Example
parallel/test-common-expect-warning
Example
parallel/test-crypto-classes
Example
parallel/test-crypto-dh
Example
parallel/test-crypto-dh-odd-key
Example
parallel/test-fs-write-stream-file-handle
Example
sequential/test-tls-session-timeout
Example
sequential/test-worker-prof
Example
Progress
Backing channel 'JNLP4-connect connection from ... is disconnected.
(10)Build timed out (after 30 minutes). Marking the build as failed.
(5)Build timed out (after 15 minutes). Marking the build as failed.
(3)ERROR: Step ?Publish JUnit test result report? failed: no workspace for ...
(5)parallel/test-module-readonly
(13)parallel/test-crypto-dh-leak
(4)sequential/test-cpu-prof-worker-argv
(4)parallel/test-child-process-fork-closed-channel-segfault
(3)parallel/test-fs-rmdir-recursive
(3)parallel/test-http-header-overflow
(3)parallel/test-net-connect-memleak
(3)sequential/test-cpu-prof-name
(3)node-api/test_threadsafe_function/test
(2)parallel/test-common-expect-warning
(2)parallel/test-crypto-classes
(2)parallel/test-crypto-dh
(2)parallel/test-crypto-dh-odd-key
(2)parallel/test-fs-write-stream-file-handle
(2)sequential/test-tls-session-timeout
(2)sequential/test-worker-prof
(2)The text was updated successfully, but these errors were encountered: