CI Reliability 2025-04-01
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/65814 to node-test-pull-request/65912 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-04-01.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-04-01 00:12 | 0 | 3 | 22 | 11 | 64 | 3.37% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-04-01.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(2) -
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(6) -
Failed to trigger node-test-commit(5) -
Unexpected token '<', ..."(4) -
pummel/test-buffer-large-size(14) -
parallel/test-file-write-stream4(5) -
sequential/test-tls-session-timeout(3) -
benchmark/test-benchmark-http2(2) -
es-module/test-typescript-eval(2) -
parallel/test-buffer-tostring-rangeerror(2) -
parallel/test-cluster-fork-stdio(2) -
sequential/test-performance-eventloopdelay(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-04-01.md and the linked node-test-pull-request build range to review the failure details. Check the unchecked entries, including pummel/test-buffer-large-size and the parallel, sequential, benchmark, and es-module tests; done is not defined beyond investigating and updating the listed CI failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100