CI Reliability 2024-06-17
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/59725 to node-test-pull-request/59820 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 |
|---|---|---|---|---|---|---|
| 2024-06-17 00:08 | 0 | 10 | 28 | 3 | 59 | 10.31% |
Jenkins Failure
| Reason | Build timed out (after 60 minutes). Marking the build as failed. |
|---|---|
| Type | JENKINS_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/53063/, https://github.com/nodejs/node/pull/53463/) |
| Appeared | test-ibm-ubi81_container-x64-1, test-digitalocean-ubi81_container-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/59769/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/59802/ |
Example
Build timed out (after 60 minutes). Marking the build as failed.
Git Failure
Build Failure
Example
fatal: No rebase in progress?
| Reason | ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/53452/, https://github.com/nodejs/node/pull/53239/, https://github.com/nodejs/node/pull/53456/) |
| Appeared | test-mnx-smartos21-x64-2, test-mnx-smartos23-x64-1, test-equinix-debian11_container-armv7l-1, test-equinix-ubuntu2004_container-armv7l-1, test-equinix-debian11_container-armv7l-2, test-osuosl-ubuntu2004_container-armv7l-1, test-osuosl-debian11_container-armv7l-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/59785/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/59797/ |
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
JSTest Failure
Example
not ok 4016 benchmark/test-benchmark-crypto
---
duration_ms: 2513.95400
severity: fail
exitcode: 1
stack: |-
node:assert:126
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
1 !== 0
at main (/home/iojs/build/workspace/node-test-commit-linux-containered/benchmark/crypto/timingSafeEqual.js:21:10)
at /home/iojs/build/workspace/node-test-commit-linux-containered/benchmark/common.js:54:9
at process.processTicksAndRejections (node:internal/process/task_queues:77:11) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: 1,
expected: 0,
operator: 'strictEqual'
}
Node.js v23.0.0-pre
node:assert:126
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
1 !== 0
at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-linux-containered/test/...
| Reason | parallel/test-pipe-file-to-http |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 5 (https://github.com/nodejs/node/pull/53429/, https://github.com/nodejs/node/pull/53157/, https://github.com/nodejs/node/pull/51344/, https://github.com/nodejs/node/pull/53464/, https://github.com/nodejs/node/pull/53472/) |
| Appeared | test-equinix-ubuntu2004_container-armv7l-1, test-equinix-debian11_container-armv7l-1, test-osuosl-ubuntu2004_container-armv7l-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/59737/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/59817/ |
Example
not ok 3840 parallel/test-pipe-file-to-http
---
duration_ms: 360046.93100
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | sequential/test-http-server-request-timeouts-mixed |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 5 (https://github.com/nodejs/node/pull/53442/, https://github.com/nodejs/node/pull/53411/, https://github.com/nodejs/node/pull/53463/, https://github.com/nodejs/node/pull/53467/, https://github.com/nodejs/node/pull/53465/) |
| Appeared | test-orka-macos11-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/59761/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/59820/ |
Example
not ok 4117 sequential/test-http-server-request-timeouts-mixed
---
duration_ms: 3456.96800
severity: fail
exitcode: 1
stack: |-
node:assert:408
throw err;
^
AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:
assert(request2.completed)
at Timeout._onTimeout (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx11-x64/test/sequential/test-http-server-request-timeouts-mixed.js:108:5)
at listOnTimeout (node:internal/timers:581:17)
at process.processTimers (node:internal/timers:519:7) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: false,
expected: true,
operator: '=='
}
Node.js v23.0.0-pre
...
| Reason | parallel/test-net-write-fully-async-buffer |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 4 (https://github.com/nodejs/node/pull/53412/, https://github.com/nodejs/node/pull/52135/, https://github.com/nodejs/node/pull/53455/, https://github.com/nodejs/node/pull/53456/) |
| Appeared | test-equinix_mnx-smartos20-x64-3, test-equinix-ubuntu2004_sharedlibs_container-arm64-4, test-equinix-rhel8_container-arm64-2, test-equinix-rhel8_container-arm64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/59725/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/59797/ |
Example
not ok 3803 parallel/test-net-write-fully-async-buffer
---
duration_ms: 300181.54700
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-worker-memory |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/53226/, https://github.com/nodejs/node/pull/53455/, https://github.com/nodejs/node/pull/53057/) |
| Appeared | test-rackspace-win2022_vs2022-x64-3, test-azure_msft-win10_vs2019-x64-3, test-rackspace-win2022_vs2022-x64-6 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/59733/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/59805/ |
Example
not ok 898 parallel/test-worker-memory
---
duration_ms: 1777.07400
severity: fail
exitcode: 3221226356
stack: |-
run() called with n=7.5 (numWorkers=8)
run() called with n=7.5 (numWorkers=8)
run() called with n=7.5 (numWorkers=8)
run() called with n=7.5 (numWorkers=8)
run() called with n=7.5 (numWorkers=8)
run() called with n=7.5 (numWorkers=8)
run() called with n=7.5 (numWorkers=8)
run() called with n=7.5 (numWorkers=8)
run() called with n=6.5 (numWorkers=8)
run() called with n=6.5 (numWorkers=8)
run() called with n=6.5 (numWorkers=8)
run() called with n=6.5 (numWorkers=8)
run() called with n=6.5 (numWorkers=8)
...
| Reason | benchmark/test-benchmark-child-process |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/53439/, https://github.com/nodejs/node/pull/53442/) |
| Appeared | test-osuosl-debian11_container-armv7l-1, test-osuosl-ubuntu2004_container-armv7l-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/59755/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/59761/ |
Example
not ok 171 benchmark/test-benchmark-child-process
---
duration_ms: 2160099.51100
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-http-get-pipeline-problem |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/53226/, https://github.com/nodejs/node/pull/53465/) |
| Appeared | test-azure_msft-win2016_vs2017-x64-2, test-azure_msft-win2016_vs2017-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/59733/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/59814/ |
Example
not ok 353 parallel/test-http-get-pipeline-problem
---
duration_ms: 337.00700
severity: fail
exitcode: 3221226505
stack: |-
image.length = 45658
recv 0
done 0
recv 1
done 1
recv 2
done 2
recv 3
done 3
recv 4
done 4
recv 5
done 5
recv 6
done 6
recv 7
done 7
recv 8
...
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(2) -
fatal: No rebase in progress?(9) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(3) -
benchmark/test-benchmark-crypto(6) -
parallel/test-pipe-file-to-http(5) -
sequential/test-http-server-request-timeouts-mixed(5) -
parallel/test-net-write-fully-async-buffer(4) -
parallel/test-worker-memory(3) -
benchmark/test-benchmark-child-process(2) -
parallel/test-http-get-pipeline-problem(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 generated ncu-ci walk pr --stats=true --markdown report and inspect the linked Jenkins console logs for each recurring failure. Trace the named benchmark and test entries, including benchmark/test-benchmark-crypto, parallel/test-pipe-file-to-http, and sequential/test-http-server-request-timeouts-mixed; done means the reported CI failures are addressed and the affected checks pass reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100