CI Reliability 2023-07-21
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, node.js
- Domain
- ci-cd, testing-qa
Research direction
Start with the listed failing entry points, including parallel/test-tls-ticket-cluster, wpt/test-structured-clone, parallel/test-runner-inspect, and the inspector and filesystem-watch tests. Reproduce failures using the linked CI jobs and inspect test/common/index.js where the performance failure points. Done means the reported CI test failures have been investigated and no longer recur across the affected jobs.
Written by the indexing model from the issue text.
Description
Failures in node-test-pull-request/52781 to node-test-pull-request/52879 that failed 2 or more 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 |
|---|---|---|---|---|---|---|
| 2023-07-21 00:14 | 1 | 0 | 28 | 2 | 69 | 0.00% |
JSTest Failure
| Reason | parallel/test-tls-ticket-cluster |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 4 (https://github.com/nodejs/node/pull/42387/, https://github.com/nodejs/node/pull/48694/, https://github.com/nodejs/node/pull/48802/, https://github.com/nodejs/node/pull/48836/) |
| Appeared | test-azure_msft-win2022_vs2019-x64-2, test-azure_msft-win2016_vs2017-x64-3, test-azure_msft-win2016_vs2017-x64-4 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52813/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52854/ |
Example
not ok 761 parallel/test-tls-ticket-cluster
---
duration_ms: 530.00000
severity: fail
exitcode: 1
stack: |-
[primary] got "listening"
[primary] connecting 54606 session? false
[primary] got "listening"
[primary] got "listening"
[primary] connecting 54606 session? false
[worker] connection reused? false
[primary] got "not-reused"
[primary] connecting 54606 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 54606 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 54606 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 54606 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 54606 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 54606 session? true
[worker] connection reused? true
[primary] got "reused"
...
| Reason | wpt/test-structured-clone |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 4 (https://github.com/nodejs/node/pull/48817/, https://github.com/nodejs/node/pull/48808/, https://github.com/nodejs/node/pull/48826/, https://github.com/nodejs/node/pull/48827/) |
| Appeared | test-azure_msft-win2016_vs2017-x64-4, test-azure_msft-win2016_vs2017-x64-1, test-azure_msft-win2016_vs2017-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52818/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52879/ |
Example
not ok 940 wpt/test-structured-clone
---
duration_ms: 318.82500
severity: fail
exitcode: 1
stack: |-
[PASS] primitive undefined
[PASS] primitive null
[PASS] primitive true
[PASS] primitive false
[PASS] primitive string, empty string
[PASS] primitive string, lone high surrogate
[PASS] primitive string, lone low surrogate
[PASS] primitive string, NUL
[PASS] primitive string, astral character
[PASS] primitive number, 0.2
[PASS] primitive number, 0
[PASS] primitive number, -0
[PASS] primitive number, NaN
[PASS] primitive number, Infinity
[PASS] primitive number, -Infinity
[PASS] primitive number, 9007199254740992
[PASS] primitive number, -9007199254740992
[PASS] primitive number, 9007199254740994
[PASS] primitive number, -9007199254740994
[PASS] primitive BigInt, 0n
[PASS] primitive BigInt, -0n
[PASS] primitive BigInt, -9007199254740994000n
[PASS] primitive BigInt, -90071992547409940009007199254740994000900719925...
| Reason | parallel/test-runner-inspect |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/48638/, https://github.com/nodejs/node/pull/48761/, https://github.com/nodejs/node/pull/48808/) |
| Appeared | test-ibm-rhel8-s390x-4, test-osuosl-rhel8-ppc64_le-4 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52842/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52868/ |
Example
not ok 3189 parallel/test-runner-inspect
---
duration_ms: 120087.56200
severity: fail
exitcode: -15
stack: |-
timeout
[test] Connecting to a child Node process
[test] Testing /json/list
[err] (node:832427) Warning: Using the inspector with --test forces running at a concurrency of 1. Use the inspectPort option to run with concurrency
[err] (Use `node --trace-warnings ...` to show where the warning was created)
[err]
[out] TAP version 13
[out]
[err] Debugger listening on ws://127.0.0.1:35619/e6298576-ed5f-4dc7-97d3-4974cd3e08fe
[err] For help, see: https://nodejs.org/en/docs/inspector
[err]
[err] Debugger attached.
[err]
[err] For help, see: https://nodejs.org/en/docs/inspector
[err]
[out] # Debugger ending on ws://127.0.0.1:35619/e6298576-ed5f-4dc7-97d3-4974cd3e08fe
[out]
...
| Reason | parallel/test-fs-watch-recursive-symlink |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48789/, https://github.com/nodejs/node/pull/48638/) |
| Appeared | test-ibm-rhel8-s390x-4 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52781/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52842/ |
Example
not ok 1380 parallel/test-fs-watch-recursive-symlink
---
duration_ms: 120058.72600
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-inspector-break-when-eval |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48638/, https://github.com/nodejs/node/pull/48834/) |
| Appeared | test-ibm-rhel8-s390x-1, test-osuosl-rhel8-ppc64_le-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52842/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52849/ |
Example
not ok 1829 parallel/test-inspector-break-when-eval
---
duration_ms: 15363.62600
severity: fail
exitcode: 1
stack: |-
[test] Connecting to a child Node process
[test] Testing /json/list
[err] Debugger listening on ws://127.0.0.1:42691/99e8a7a3-13fc-4d61-acc9-617c6db605e9
[err] For help, see: https://nodejs.org/en/docs/inspector
[err]
[test] Setting up a debugger
[err] Debugger attached.
[err]
Timed out waiting for matching notification (Initial pause)
1
...
| Reason | parallel/test-inspector-wait-for-connection |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48779/, https://github.com/nodejs/node/pull/48559/) |
| Appeared | test-nearform-macos10.15-x64-3, test-nearform-macos10.15-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52790/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52839/ |
Example
not ok 1792 parallel/test-inspector-wait-for-connection
---
duration_ms: 15792.04000
severity: fail
exitcode: 1
stack: |-
[test] Connecting to a child Node process
[test] Testing /json/list
[err] Debugger listening on ws://127.0.0.1:65471/7249582f-9236-40cb-93b1-ee20ad046d7c
[err] For help, see: https://nodejs.org/en/docs/inspector
[err]
[err] Debugger attached.
[err]
[out] before wait for debugger
[out]
Timed out waiting for matching notification (Console output matching "after wait for debugger")
1
...
| Reason | parallel/test-performance-function |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/47150/, https://github.com/nodejs/node/pull/48761/) |
| Appeared | test-ibm-ubuntu1804-x64-2, undefined |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52793/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52838/ |
Example
not ok 2288 parallel/test-performance-function
---
duration_ms: 177.17500
severity: fail
exitcode: 1
stack: |-
node:internal/errors:496
ErrorCaptureStackTrace(err);
^
RangeError [ERR_OUT_OF_RANGE]: The value of "val" is out of range. It must be >= 1 && <= 9007199254740991. Received 0
at RecordableHistogram.record (node:internal/histogram:283:5)
at processComplete (node:internal/perf/timerify:40:15)
at timerified m (node:internal/perf/timerify:87:5)
at /home/iojs/build/workspace/node-test-commit-linux/test/parallel/test-performance-function.js:98:5 {
code: 'ERR_OUT_OF_RANGE'
}
Node.js v20.5.0
...
| Reason | sequential/test-https-server-keep-alive-timeout |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48808/, https://github.com/nodejs/node/pull/48694/) |
| Appeared | test-ibm-rhel8-s390x-4, test-equinix-ubuntu2004_container-armv7l-1, undefined |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52806/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52816/ |
Example
not ok 3825 sequential/test-https-server-keep-alive-timeout
---
duration_ms: 984.78900
severity: fail
exitcode: 1
stack: |-
Mismatched <anonymous> function calls. Expected exactly 3, actual 1.
at Proxy.mustCall (/home/iojs/build/workspace/node-test-commit-linuxone/test/common/index.js:410:10)
at serverKeepAliveTimeoutWithPipeline (/home/iojs/build/workspace/node-test-commit-linuxone/test/sequential/test-https-server-keep-alive-timeout.js:34:12)
at run (/home/iojs/build/workspace/node-test-commit-linuxone/test/sequential/test-https-server-keep-alive-timeout.js:28:11)
at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
...
| Reason | sequential/test-worker-prof |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48838/, https://github.com/nodejs/node/pull/48828/) |
| Appeared | test-azure_msft-win2022_vs2019-x64-4, test-rackspace-win2012r2_vs2019-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52858/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52876/ |
Example
not ok 936 sequential/test-worker-prof
---
duration_ms: 30324.59000
severity: fail
exitcode: 1
stack: |-
node:assert:125
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: child exited with signal: {
error: Error: spawnSync C:\workspace\node-test-binary-windows-js-suites\node\Release\node.exe ETIMEDOUT
at Object.spawnSync (node:internal/child_process:1124:20)
at spawnSync (node:child_process:876:24)
at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\sequential\test-worker-prof.js:53:23)
at Module._compile (node:internal/modules/cjs/loader:1233:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1287:10)
at Module.load (node:internal/modules/cjs/loader:1091:32)
at Module._load (node:internal/modules/cjs/loader:938:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
at node:internal/main/ru...
Jenkins Failure
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 119.9.51.79/119.9.51.79:47362' is disconnected.
at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:215)
at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:285)
at jdk.proxy2/jdk.proxy2.$Proxy116.isAlive(Unknown Source)
at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1215)
at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1207)
CCTest Failure
| Reason | C:\workspace\node-compile-windows\node\test\cctest\test_inspector_socket.cc(323): error: Value of: (!expectation.read_expected) |
|---|---|
| Type | CC_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48761/, https://github.com/nodejs/node/pull/48708/) |
| Appeared | test-rackspace-win2022_vs2022-x64-3, test-rackspace-win2012r2_vs2019-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52791/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52871/ |
Example
C:\workspace\node-compile-windows\node\test\cctest\test_inspector_socket.cc(323): error: Value of: (!expectation.read_expected)
Actual: true
Expected: false
[ FAILED ] InspectorSocketTest.HostIPv6NonRoutable (5001 ms)
Git Failure
Build Failure
Example
fatal error: Killed signal terminated program cc1plus
| Reason | ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 4 (https://github.com/nodejs/node/pull/42387/, https://github.com/nodejs/node/pull/48721/, https://github.com/nodejs/node/pull/48779/, https://github.com/nodejs/node/pull/48808/) |
| Appeared | test-equinix-ubuntu2004_container-armv7l-2, test-equinix_mnx-smartos20-x64-3, test-osuosl-aix72-ppc64_be-3, test-equinix-rhel8_container-arm64-1, test-equinix-ubuntu1804_sharedlibs_container-arm64-1, test-equinix-ubuntu2004_container-arm64-2, test-osuosl-ubuntu2004_container-armv7l-1, test-equinix-ubuntu2004_sharedlibs_container-arm64-5, test-equinix-debian10_container-armv7l-2, test-equinix-ubuntu2004_container-armv7l-1, test-osuosl-debian10_container-armv7l-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52786/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52806/ |
Example
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
[PostBuildScript] - [INFO] Executing post build scripts.
[node-test-binary-armv7l] $ /bin/bash -ex /tmp/jenkins17324078198030927393.sh
+ '[' -d .git ']'
+ git clean -fdx
Removing benchmark/napi/.buildstamp
| Reason | Error: list index out of range |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/42387/, https://github.com/nodejs/node/pull/48721/, https://github.com/nodejs/node/pull/48779/) |
| Appeared | test-equinix-debian10_container-armv7l-1, test-equinix-debian10_container-armv7l-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52786/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52796/ |
Example
Error: list index out of range
+ true
+ tap2junit -i cctest.tap -o out/junit/cctest.xml
usage: tap2junit [-h] --input INPUT --output OUTPUT [--compact] [--name NAME]
[--package PACKAGE]
tap2junit: error: argument --input/-i: can't open 'cctest.tap': [Errno 2] No such file or directory: 'cctest.tap'
| Reason | ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error? |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48761/, https://github.com/nodejs/node/pull/48808/) |
| Appeared | test-azure_msft-win11_vs2022-arm64-3, test-rackspace-win2012r2_vs2019-x64-2, test-azure_msft-win2016_vs2017-x64-3, test-azure_msft-win2022_vs2019-x64-1, test-azure_msft-win2022_vs2019-x64-3, test-rackspace-win2012r2_vs2015-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52791/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52806/ |
Example
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE
| Reason | fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48735/, https://github.com/nodejs/node/pull/48779/) |
| Appeared | test-equinix-ubuntu2004_container-armv7l-1, test-equinix-ubuntu2004_container-armv7l-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52789/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52796/ |
Example
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository
fatal: Could not read from remote repository.
fatal: failed to run repack
Progress
-
parallel/test-tls-ticket-cluster(4) -
wpt/test-structured-clone(4) -
parallel/test-runner-inspect(3) -
parallel/test-fs-watch-recursive-symlink(2) -
parallel/test-inspector-break-when-eval(2) -
parallel/test-inspector-wait-for-connection(2) -
parallel/test-performance-function(2) -
sequential/test-https-server-keep-alive-timeout(2) -
sequential/test-worker-prof(2) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(13) -
C:\workspace\node-compile-windows\node\test\cctest\test_inspector_socket.cc(323): error: Value of: (!expectation.read_expected)(2) -
fatal error: Killed signal terminated program cc1plus(11) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(4) -
Error: list index out of range(3) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(2) -
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository(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 75/100
-
Update Vish to 1.1.5 Openpackage-update
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oSoWoSo/vOid_Community_repOsitory#144 · 1 comment ·