CI Reliability 2024-09-24
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/62612 to node-test-pull-request/62709 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-09-24.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-09-24 00:09 | 17 | 20 | 11 | 13 | 39 | 28.57% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-09-24.md to see failure details
Progress
-
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository(5) -
fatal: No rebase in progress?(4) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
Failed to trigger sub builds(2) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj](2) -
parallel/test-file-write-stream4(3) -
parallel/test-http2-large-write-multiple-requests(3) -
parallel/test-inspector-strip-types(3) -
parallel/test-net-write-fully-async-buffer(3) -
node-api/test_threadsafe_function/test(2) -
parallel/test-crypto-worker-thread(2) -
parallel/test-http-remove-header-stays-removed(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
Review reports/2024-09-24.md and the linked Jenkins failures from node-test-pull-request/62612 through 62709. Start with the failure details generated by ncu-ci walk pr --stats=true --markdown reports/2024-09-24.md, then investigate the listed recurring failures. Done means the identified CI failures are addressed and the affected checks no longer recur.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100