CI Reliability 2025-05-21
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/66873 to node-test-pull-request/66968 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-05-21.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-05-21 00:11 | 0 | 12 | 13 | 0 | 75 | 12.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-05-21.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(3) -
fatal: No rebase in progress?(12) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(3) -
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(16) -
parallel/test-buffer-tostring-rangeerror(13) -
parallel/test-buffer-tostring-range(10) -
parallel/test-repl-multiline-navigation(7) -
parallel/test-runner-run-watch(5) -
async-hooks/test-emit-after-on-destroyed(4) -
parallel/test-runner-output(2) -
parallel/test-stream-readable-to-web(2) -
parallel/test-worker-nearheaplimit-deadlock(2) -
parallel/test-zlib-brotli-16GB(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
Start with reports/2025-05-21.md and the linked node-test-pull-request runs to inspect the listed failures. The report was generated with ncu-ci walk pr --stats=true --markdown reports/2025-05-21.md; use that output and the referenced test names to identify the failures. Done is not defined beyond addressing the reported CI failures and restoring reliable green runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100