CI Reliability 2025-03-05
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/65485 to node-test-pull-request/65576 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-03-05.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-03-05 00:10 | 2 | 12 | 22 | 8 | 56 | 13.33% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-03-05.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(2) -
ERROR: Error fetching remote repo 'origin'(5) -
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?(9) -
Failed to trigger sub builds(4) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
fatal: no rebase in progress(2) -
sh: line 12: [: -gt: unary operator expected(2) -
parallel/test-assert-fail(16) -
parallel/test-runner-run-watch(11) -
parallel/test-file-write-stream4(7) -
sequential/test-perf-hooks(3) -
parallel/test-buffer-tostring-rangeerror(2) -
parallel/test-fs-cp(2) -
parallel/test-fs-watch-recursive-delete(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-03-05.md and inspect the linked node-test-pull-request builds for the repeated failure details. Work through the listed CI errors and failing Node.js tests, with completion indicated by the affected failures being resolved and the CI results becoming green.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100