CI Reliability 2022-04-04
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, nodejs, shell
- Domain
- ci-cd, devops, testing-qa
Research direction
Start by reviewing the linked Jenkins job logs and the listed CI failure categories, including the referenced Node.js test names and runner hosts. The issue names no source files, fix scope, or acceptance criteria, so what counts as done is not defined beyond investigating the unchecked progress items.
Written by the indexing model from the issue text.
Description
Failures in node-test-pull-request/43208 to node-test-pull-request/43293 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-04 00:11 | 10 | 7 | 22 | 23 | 38 | 10.45% |
Jenkins Failure
| Reason | Backing channel 'JNLP4-connect connection from ... is disconnected. |
|---|---|
| Type | JENKINS_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/42115/, https://github.com/nodejs/node/pull/42567/, https://github.com/nodejs/node/pull/41513/) |
| Appeared | test-digitalocean-freebsd12-x64-2, test-equinix-ubuntu2004_container-armv7l-1, test-equinix-centos7_container-arm64-2, test-equinix-ubuntu1804_container-arm64-2, test-equinix-ubuntu2004_container-arm64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/43234/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/43280/ |
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 107.170.28.213/107.170.28.213:59408' 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 5 minutes). Marking the build as aborted. |
|---|---|
| Type | JENKINS_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/42494/, https://github.com/nodejs/node/pull/42583/) |
| Appeared | test-equinix-ubuntu2004_container-armv7l-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/43224/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/43283/ |
Example
Build timed out (after 5 minutes). Marking the build as aborted.
Git Failure
Build Failure
| Reason | ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/38545/, https://github.com/nodejs/node/pull/42387/, https://github.com/nodejs/node/pull/41513/) |
| Appeared | test-digitalocean-freebsd12-x64-2, test-nearform-macos11.0-arm64-1, test-orka-macos10.15-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/43222/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/43289/ |
Example
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for node-test-commit-freebsd/nodes=freebsd12-x64 #43476
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE
| Reason | Failed to trigger node-test-commit |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/43206/, https://github.com/nodejs/node/pull/42514/) |
| Appeared | test-packetnet-ubuntu1804-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/43208/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/43293/ |
Example
Failed to trigger node-test-commit
undefined
Example
Unknown
JSTest Failure
| Reason | parallel/test-crypto-secure-heap |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/42507/, https://github.com/nodejs/node/pull/42584/) |
| Appeared | test-requireio_rvagg-debian10-armv7l_pi2-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/43226/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/43274/ |
Example
not ok 282 parallel/test-crypto-secure-heap
---
duration_ms: 360.68
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-fetch |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/41263/, https://github.com/nodejs/node/pull/42583/) |
| Appeared | test-requireio_rvagg-debian10-armv7l_pi2-1, test-equinix-ubuntu1804_sharedlibs_container-arm64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/43232/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/43283/ |
Example
not ok 260 parallel/test-fetch
---
duration_ms: 384.363
severity: fail
exitcode: -15
stack: |-
timeout
(node:20131) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
...
| Reason | parallel/test-net-connect-memleak |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/42512/, https://github.com/nodejs/node/pull/42584/) |
| Appeared | test-rackspace-win2012r2_vs2017-x64-4, test-azure_msft-win2016_vs2017-x64-3 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/43225/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/43274/ |
Example
not ok 466 parallel/test-net-connect-memleak
---
duration_ms: 0.265
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:369: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:1106:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1160:10)
at Module.load (node:internal/modules/cjs/loader:982:32)
at Function.Module._load (node:internal/modules/cjs/loader:829:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
at node:internal/main/run_main_module:17:47
...
| 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.(3) -
Build timed out (after 5 minutes). Marking the build as aborted.(2) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(3) -
Failed to trigger node-test-commit(2) -
Unknown(6) -
parallel/test-crypto-secure-heap(2) -
parallel/test-fetch(2) -
parallel/test-net-connect-memleak(2) -
parallel/test-vm-timeout-escape-promise-2(2)
- Dominant language
- Shell
- Stars
- 57
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
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.
More from nodejs/reliability
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
nodejs/reliability#1666 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
nodejs/reliability#1665 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
nodejs/reliability#1664 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
nodejs/reliability#1663 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
nodejs/reliability#1662 ·
All issues in nodejs/reliability
Similar issues
-
out-of-date
Difficulty 1/5 Under an hour Newbie friendliness 82/100
CachyOS/CachyOS-PKGBUILDS#1894 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
community-scripts/ProxmoxVE#17396 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mattpocock/skills#1099 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100