CI Reliability 2025-05-22
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/66894 to node-test-pull-request/66993 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-05-22.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-05-22 00:11 | 0 | 13 | 15 | 0 | 72 | 13.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-05-22.md to see failure details
Progress
-
fatal: No rebase in progress?(8) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(3) -
parallel/test-http2-debug(19) -
pummel/test-blob-slice-with-large-size(15) -
parallel/test-buffer-tostring-rangeerror(14) -
parallel/test-buffer-tostring-range(8) -
async-hooks/test-emit-after-on-destroyed(4) -
parallel/test-repl-multiline-navigation(3) -
parallel/test-runner-run-watch(3) -
parallel/test-runner-output(2) -
parallel/test-stream-readable-to-web(2) -
wpt/test-timers(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
Read reports/2025-05-22.md and the linked CI runs first to find the failure details behind each listed category. Reproduce the affected Node.js tests where possible, then address the failures and confirm the listed CI errors no longer recur.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, 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