CI Reliability 2025-02-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/64953 to node-test-pull-request/65047 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-02-08.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-02-08 00:09 | 0 | 22 | 14 | 10 | 54 | 24.44% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-02-08.md to see failure details
Progress
-
parallel/test-assert-fail(11) -
parallel/test-runner-run-watch(10) -
parallel/test-file-write-stream4(5) -
parallel/test-net-write-fully-async-buffer(4) -
parallel/test-runner-output(2) -
parallel/test-without-async-context-frame(2) -
parallel/test-zlib-brotli-16GB(2) -
sequential/test-perf-hooks(2) -
sequential/test-performance-eventloopdelay(2) -
sequential/test-tls-session-timeout(2) -
ERROR: Error fetching remote repo 'origin'(3) -
Error: list index out of range(4) -
error: remote GitHub already exists.(3) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
Failed to trigger sub builds(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
Start with the linked reports/2025-02-08.md report and the referenced node-test-pull-request jobs to inspect failure details. Reproduce the listed failures, beginning with the parallel and sequential tests in the Progress list, and use the report to track which recurring CI failures have been resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, 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