CI Reliability 2025-02-17
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/65162 to node-test-pull-request/65264 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-02-17.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-02-17 00:10 | 0 | 12 | 10 | 7 | 71 | 12.90% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-02-17.md to see failure details
Progress
-
parallel/test-assert-fail(9) -
parallel/test-buffer-tostring-rangeerror(9) -
parallel/test-runner-run-watch(8) -
parallel/test-file-write-stream4(3) -
benchmark/test-benchmark-http2(2) -
parallel/test-http-get-pipeline-problem(2) -
wpt/test-timers(2) -
Build timed out (after 30 minutes). Marking the build as failed.(4) -
ERROR: Error fetching remote repo 'origin'(2) -
fatal: detected dubious ownership in repository at 'C:/workspace/node-test-binary-windows-js-suites/build'(8) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(6) -
fatal: No rebase in progress?(6) -
sh: line 9: [: -gt: unary operator expected(3) -
Failed to trigger node-test-commit(2) -
fatal: detected dubious ownership in repository at 'C:/workspace/node-test-binary-windows-native-suites/build'(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-02-17.md and the linked node-test-pull-request builds to inspect the failure details. Review the listed test failures, build errors, and Git-related errors in the report; done means the tracked failures are addressed and the affected CI runs no longer reproduce them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100