CI Reliability 2025-05-19
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/66817 to node-test-pull-request/66914 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-05-19.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-05-19 00:12 | 1 | 19 | 9 | 0 | 71 | 19.19% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-05-19.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(8) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
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(19) -
parallel/test-buffer-tostring-range(16) -
parallel/test-buffer-tostring-rangeerror(9) -
parallel/test-repl-multiline-navigation(9) -
parallel/test-runner-run-watch(5) -
parallel/test-stream-readable-to-web(3) -
sequential/test-buffer-creation-regression(3) -
sequential/test-perf-hooks(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 node-test-pull-request jobs and the reliability report at reports/2025-05-19.md. Review the repeated timeout, repository, rebase, test-report, and named Node.js test failures, then use the listed progress items to track investigation. Done means the reported recurring CI failures are addressed and subsequent runs no longer reproduce them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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