CI Reliability 2025-05-23
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/66911 to node-test-pull-request/67009 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-05-23.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-05-23 00:11 | 0 | 16 | 16 | 0 | 68 | 16.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-05-23.md to see failure details
Progress
-
fatal: No rebase in progress?(7) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
parallel/test-http2-debug(19) -
parallel/test-buffer-tostring-rangeerror(13) -
pummel/test-blob-slice-with-large-size(13) -
parallel/test-buffer-tostring-range(9) -
async-hooks/test-emit-after-on-destroyed(4) -
async-hooks/test-improper-unwind(3) -
parallel/test-runner-output(2) -
parallel/test-worker-nearheaplimit-deadlock(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 by reading reports/2025-05-23.md and the linked CI job results for the listed failures. Use the generated ncu-ci walk pr --stats=true --markdown command context to trace each recurring failure, then update the checklist as the affected CI failures are resolved and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100