CI Reliability 2025-06-08
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/67225 to node-test-pull-request/67321 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-06-08.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-06-08 00:12 | 0 | 12 | 29 | 5 | 54 | 12.63% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-06-08.md to see failure details
Progress
-
sequential/test-performance-eventloopdelay(5) -
parallel/test-buffer-tostring-range(3) -
parallel/test-performance-eventlooputil(3) -
es-module/test-vm-contextified-script-leak(2) -
parallel/test-runner-run-watch(2) -
parallel/test-without-async-context-frame(2) -
wpt/test-streams(2) -
Build timed out (after 30 minutes). Marking the build as failed.(4) -
ERROR: Error fetching remote repo 'origin'(4) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
Error: HEAD does not match expected COMMIT_SHA_CHECK'(2) -
Failed to trigger node-test-commit(2) -
error: remote GitHub already exists.(2) -
fatal: No rebase in progress?(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-06-08.md and the linked node-test-pull-request builds first, using the listed ncu-ci walk command as context. Investigate the failures in the Progress list and determine their causes across the affected CI jobs. Done means the listed reliability failures are resolved and the progress checklist reflects the results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100