CI Reliability 2024-12-03
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/63744 to node-test-pull-request/63843 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-12-03.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-12-03 00:11 | 0 | 11 | 24 | 0 | 65 | 11.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-12-03.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(5) -
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository(3) -
fatal: No rebase in progress?(3) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
Error: - process terminated with status 1, expected 0(2) -
fatal error: 'ranges' file not found(2) -
sequential/test-http-server-request-timeouts-mixed(15) -
parallel/test-file-write-stream4(6) -
parallel/test-net-write-fully-async-buffer(3) -
parallel/test-stream-readable-unpipe-resume(3) -
parallel/test-watch-file-shared-dependency(3) -
wpt/test-compression(3) -
parallel/test-runner-run(2) -
parallel/test-timers-immediate-queue(2) -
parallel/test-watch-mode-files_watcher(2) -
sequential/test-tls-session-timeout(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/2024-12-03.md and the linked node-test-pull-request runs, then use the generated ncu-ci walk pr --stats=true --markdown command to inspect each failure category. Trace the listed repository, ccache, reporting, and test failures to their CI configuration or tests. Done means the reported recurring failures are addressed and the affected CI runs no longer reproduce them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100