CI Reliability 2025-03-30
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/65797 to node-test-pull-request/65896 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-03-30.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-03-30 00:11 | 0 | 3 | 23 | 9 | 65 | 3.30% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-03-30.md to see failure details
Progress
-
Command "git fetch --tags --force --progress -- binary_tmp@67.158.54.159:binary_tmp.git +refs/heads/jenkins-node-test-commit-arm-fanned-4d0b4e70773:refs/remotes/jenkins_tmp/_jenkins_local_branch" returned status code 128:(2) -
Error: list index out of range(5) -
Failed to trigger node-test-commit(5) -
error: remote GitHub already exists.(3) -
Unexpected token '<', ..."(6) -
pummel/test-buffer-large-size(13) -
parallel/test-file-write-stream4(3) -
benchmark/test-benchmark-http2(2) -
parallel/test-buffer-tostring-rangeerror(2) -
parallel/test-runner-run-watch(2) -
parallel/test-stream-readable-unpipe-resume(2) -
sequential/test-performance-eventloopdelay(2) -
sequential/test-tls-session-timeout(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 reports/2025-03-30.md and the linked node-test-pull-request Jenkins runs, then use the ncu-ci walk pr --stats=true --markdown command context to inspect each failure signature. Done means the listed CI failures have been investigated and the corresponding progress items can be checked off.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, node.js, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100