CI Reliability 2025-05-20
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/66857 to node-test-pull-request/66956 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-05-20.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-05-20 00:12 | 0 | 12 | 9 | 0 | 79 | 12.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-05-20.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(4) -
ERROR: Error fetching remote repo 'origin'(3) -
fatal: No rebase in progress?(14) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(6) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
parallel/test-http2-debug(20) -
pummel/test-blob-slice-with-large-size(17) -
parallel/test-buffer-tostring-range(12) -
parallel/test-buffer-tostring-rangeerror(12) -
parallel/test-repl-multiline-navigation(9) -
parallel/test-runner-run-watch(5) -
async-hooks/test-emit-after-on-destroyed(4) -
sequential/test-buffer-creation-regression(3) -
parallel/test-stream-readable-to-web(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 with reports/2025-05-20.md and the linked node-test-pull-request jobs to inspect details for the repeated failures. Review the listed timeout, repository-fetch, rebase, JUnit-report, and test failures, then use the Progress checklist to track which issues are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100