CI Reliability 2025-02-28
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/65374 to node-test-pull-request/65471 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-02-28.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-02-28 00:10 | 5 | 15 | 19 | 7 | 54 | 17.05% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-02-28.md to see failure details
Progress
-
sh: line 12: [: -gt: unary operator expected(5) -
fatal: No rebase in progress?(3) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
Failed to trigger sub builds(2) -
parallel/test-assert-fail(8) -
parallel/test-file-write-stream4(7) -
parallel/test-runner-run-watch(7) -
parallel/test-http-server-headers-timeout-keepalive(3) -
sequential/test-tls-session-timeout(3) -
parallel/test-zlib-brotli-16GB(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
Review reports/2025-02-28.md and the linked CI runs, beginning with the listed failure signatures. The issue does not define a single fix or completion criterion; investigate the affected failures and verify that the relevant pull-request CI runs become green.
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