CI Reliability 2026-06-02
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/73780 to node-test-pull-request/73875 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-06-02.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-06-02 00:40 | 0 | 21 | 25 | 5 | 49 | 22.11% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-06-02.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(6) -
Command "git reset --hard" returned status code 128:(2) -
Failed to trigger sub builds(6) -
fatal: No rebase in progress?(5) -
parallel/test-fs-watch-recursive-delete(4) -
parallel/test-http2-close-while-writing(3) -
test-runner/test-run-watch-cwd-isolation-none(2) -
wpt/test-hr-time(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/2026-06-02.md and the linked node-test-pull-request runs. Use the eight unchecked failure entries as the investigation checklist, beginning with the repeated Git and sub-build errors. Done means the listed failures have been investigated and the corresponding progress entries can be updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100