CI Reliability 2024-09-26
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/62676 to node-test-pull-request/62772 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-09-26.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-09-26 00:09 | 2 | 21 | 23 | 7 | 47 | 23.08% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-09-26.md to see failure details
Progress
-
node-api/test_threadsafe_function/test(9) -
parallel/test-stream-readable-unpipe-resume(4) -
parallel/test-http2-large-write-multiple-requests(3) -
parallel/test-net-write-fully-async-buffer(3) -
parallel/test-inspector-strip-types(2) -
Error: invalid syntax(5) -
fatal: No rebase in progress?(5) -
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository(3) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(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
Open reports/2024-09-26.md first and review the linked CI failure details for the listed tests and errors. Work through the failures affecting multiple PRs, using the progress checklist as the scope. Done means the listed reliability 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, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100