CI Reliability 2025-05-18
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/66773 to node-test-pull-request/66871 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-05-18.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-05-18 00:12 | 1 | 15 | 12 | 2 | 70 | 15.46% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-05-18.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(8) -
Build timed out (after 60 minutes). Marking the build as failed.(4) -
ERROR: Error fetching remote repo 'origin'(4) -
fatal: No rebase in progress?(6) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(4) -
Failed to trigger node-test-commit(3) -
fatal error: Killed signal terminated program cc1plus(2) -
pummel/test-blob-slice-with-large-size(17) -
parallel/test-buffer-tostring-range(14) -
parallel/test-http2-debug(8) -
parallel/test-crypto-async-sign-verify(4) -
parallel/test-repl-multiline-navigation(3) -
parallel/test-worker-nearheaplimit-deadlock(3) -
sequential/test-buffer-creation-regression(3) -
sequential/test-tls-session-timeout(3) -
parallel/test-async-context-frame(2) -
parallel/test-esm-loader-hooks-inspect-wait(2) -
parallel/test-fs-read-stream(2) -
parallel/test-http-server-headers-timeout-keepalive(2) -
sequential/test-perf-hooks(2) -
sequential/test-performance-eventloopdelay(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-05-18.md and the linked node-test-pull-request builds 66773–66871 to inspect the listed timeout, repository, trigger, and test failures. Trace the repeated failures to their CI or test source; done means the contributing failures are addressed and the affected jobs no longer reproduce them.
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
- 25/100