CI Reliability 2024-09-22
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/62554 to node-test-pull-request/62650 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-09-22.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-09-22 00:10 | 2 | 15 | 22 | 10 | 51 | 17.05% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-09-22.md to see failure details
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(2) -
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository(7) -
fatal: No rebase in progress?(7) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(2) -
Failed to trigger sub builds(2) -
fatal error: Killed signal terminated program cc1plus(2) -
node-api/test_threadsafe_function/test(7) -
es-module/test-loaders-workers-spawned(5) -
parallel/test-async-context-frame(4) -
parallel/test-http2-large-write-multiple-requests(4) -
parallel/test-file-write-stream4(3) -
parallel/test-http-remove-header-stays-removed(3) -
parallel/test-net-write-fully-async-buffer(3) -
parallel/test-runner-watch-mode-complex(3) -
parallel/test-buffer-tostring-rangeerror(2) -
parallel/test-stream-readable-unpipe-resume(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 generated report at reports/2024-09-22.md and the failure range from node-test-pull-request/62554 to 62650. Use the listed failure messages and test names to determine which CI failures need follow-up; the payload does not define a narrower completion criterion.
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