CI Reliability 2025-03-28
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/65795 to node-test-pull-request/65894 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-03-28.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-03-28 00:10 | 0 | 3 | 24 | 9 | 64 | 3.30% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-03-28.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 C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj](4) -
error: remote GitHub already exists.(3) -
sh: line 12: [: -gt: unary operator expected(2) -
Unexpected token '<', ..."(5) -
pummel/test-buffer-large-size(12) -
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)
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 reliability report at reports/2025-03-28.md and inspect the Jenkins job range from node-test-pull-request/65795 to /65894. Review the listed failures and affected tests, then use the Progress checklist to track investigation. Done means the identified CI failures are resolved or have clear follow-up issues.
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
- 25/100