CI Reliability 2024-09-25
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/62655 to node-test-pull-request/62753 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-09-25.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-09-25 00:09 | 2 | 19 | 20 | 9 | 50 | 21.35% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-09-25.md to see failure details
Progress
-
node-api/test_threadsafe_function/test(9) -
parallel/test-net-write-fully-async-buffer(4) -
parallel/test-stream-readable-unpipe-resume(4) -
parallel/test-inspector-strip-types(3) -
fatal: No rebase in progress?(7) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(3) -
Error: invalid syntax(3) -
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository(3)
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 reliability report for the failures from node-test-pull-request/62655 through 62753 and review the eight items listed under Progress. Use the named test paths and CI errors to identify the failing jobs; done means the listed recurring failures are resolved and the affected CI runs are reliable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100