CI Reliability 2022-04-02
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 57
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Failures in node-test-pull-request/43162 to node-test-pull-request/43259 that failed more than 2 PRs
(Generated with ncu-ci walk pr --stats=true --markdown /home/runner/work/reliability/reliability/results.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2022-04-02 00:11 | 1 | 4 | 27 | 19 | 49 | 5.00% |
Jenkins Failure
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 139.178.85.13/139.178.85.13:47766' 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 60 minutes). Marking the build as failed. |
|---|---|
| Type | JENKINS_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/42466/, https://github.com/nodejs/node/pull/42410/) |
| Appeared | test-softlayer-ubi81_container-x64-1, test-rackspace-win2012r2_vs2019-x64-4 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/43183/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/43191/ |
Example
Build timed out (after 60 minutes). Marking the build as failed.
Git Failure
Build Failure
| Reason | Failed to trigger node-test-commit |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/42399/, https://github.com/nodejs/node/pull/43206/) |
| Appeared | test-packetnet-ubuntu1804-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/43184/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/43208/ |
Example
Failed to trigger node-test-commit
undefined
Example
Unknown
JSTest Failure
| Reason | parallel/test-child-process-fork-closed-channel-segfault |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/42442/, https://github.com/nodejs/node/pull/42486/) |
| Appeared | test-requireio_securogroup-debian10-arm64_pi3-2, test-requireio_jasnell-debian10-armv7l_pi2-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/43175/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/43198/ |
Example
not ok 106 parallel/test-child-process-fork-closed-channel-segfault
---
duration_ms: 3.784
severity: fail
exitcode: 1
stack: |-
/home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-child-process-fork-closed-channel-segfault.js:83
throw err;
^
Error: write EPIPE
at ChildProcess.target._send (node:internal/child_process:864:20)
at ChildProcess.<anonymous> (node:internal/child_process:667:16)
at ChildProcess.emit (node:events:539:35)
at emit (node:internal/child_process:936:14)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
errno: -32,
code: 'EPIPE',
syscall: 'write'
}
Node.js v18.0.0-pre
...
| Reason | parallel/test-crypto-keygen |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/42360/, https://github.com/nodejs/node/pull/42054/) |
| Appeared | test-digitalocean-ubuntu1804_sharedlibs_container-x64-3, test-softlayer-ubuntu1804_sharedlibs_container-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/43170/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/43187/ |
Example
not ok 1637 parallel/test-crypto-keygen
---
duration_ms: 120.75
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-http-header-overflow |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/42360/, https://github.com/nodejs/node/pull/41263/) |
| Appeared | test-equinix-ubuntu1804_sharedlibs_container-arm64-1, test-rackspace-win2012r2_vs2013-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/43164/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/43232/ |
Example
not ok 1015 parallel/test-http-header-overflow
---
duration_ms: 0.431
severity: crashed
exitcode: -6
stack: |-
Found bad BaseObject during clean exit: ConnectionsList
1: 0xaaaad17311e8 node::DumpBacktrace(_IO_FILE*) [out/Debug/node]
2: 0xaaaad181d748 node::Abort() [out/Debug/node]
3: 0xaaaad1754004 [out/Debug/node]
4: 0xaaaad1761058 [out/Debug/node]
5: 0xaaaad175409c node::Environment::VerifyNoStrongBaseObjects() [out/Debug/node]
6: 0xaaaad16c5194 node::SpinEventLoop(node::Environment*) [out/Debug/node]
7: 0xaaaad188faf0 node::NodeMainInstance::Run(int*, node::Environment*) [out/Debug/node]
8: 0xaaaad188fa34 node::NodeMainInstance::Run() [out/Debug/node]
9: 0xaaaad17bf870 node::Start(int, char**) [out/Debug/node]
10: 0xaaaad2d3a214 main [out/Debug/node]
11: 0xffffa0eae720 __libc_start_main [/lib/aarch64-linux-gnu/libc.so.6]
12: 0xaaaad16bf8b0 [out/Debug/node]
...
| Reason | parallel/test-trace-events-fs-sync |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/42471/, https://github.com/nodejs/node/pull/42466/) |
| Appeared | test-azure_msft-win10_vs2019-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/43193/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/43218/ |
Example
not ok 695 parallel/test-trace-events-fs-sync
---
duration_ms: 1.993
severity: fail
exitcode: 1
stack: |-
Can't clean tmpdir: C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.691
Files blocking: [ 'fs.txt', 'node_trace.1.log' ]
C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-trace-events-fs-sync.js:133
throw new Error(`${tr}:\n${util.inspect(proc)}`);
^
Error: fs.sync.fstat:
{
status: 1,
signal: null,
output: [
null,
'',
'node:internal/fs/utils:345\r\n' +
' throw err;\r\n' +
' ^\r\n' +
'\r\n' +
"Error: EPERM: operation not permitted, open 'fs.txt'\r\n" +
' at Object.openSync (node:fs:584:3)\r\n' +
' at Object.writeFileSync (node:fs:2169:35)\r\n' +
' at [eval]:1:4\r\n' +
' at Script.runInThisContext (node:vm:129:12)\r\n' +
' at Object.runInThisContext (node:vm:305:38)...
| Reason | parallel/test-vm-timeout-escape-promise-2 |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/42115/, https://github.com/nodejs/node/pull/42466/) |
| Appeared | test-ibm-rhel8-s390x-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/43234/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/43237/ |
Example
not ok 2704 parallel/test-vm-timeout-escape-promise-2
---
duration_ms: 0.239
severity: fail
exitcode: 1
stack: |-
/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-vm-timeout-escape-promise-2.js:20
throw new Error(
^
Error: escaped timeout at 100 milliseconds!
at loop (/home/iojs/build/workspace/node-test-commit-linuxone/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 (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-vm-timeout-escape-promise-2.js:27:6)
at getActual (node:assert:756:5)
at Function.throws (node:assert:902:24)
at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-vm-timeout-escape-promise-2.js:26:8)
...
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(4) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
Failed to trigger node-test-commit(2) -
Unknown(8) -
parallel/test-child-process-fork-closed-channel-segfault(2) -
parallel/test-crypto-keygen(2) -
parallel/test-http-header-overflow(2) -
parallel/test-trace-events-fs-sync(2) -
parallel/test-vm-timeout-escape-promise-2(2)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Jenkins console logs and the generated failure summary, then compare the affected nodes and PR runs. The report names tests such as test/parallel/test-child-process-fork-closed-channel-segfault.js and test/parallel/test-trace-events-fs-sync.js; done means identifying and resolving the recurring CI failures so the affected checks become reliable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100