CI Reliability 2024-09-12
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/62215 to node-test-pull-request/62334 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-09-12.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-09-12 00:09 | 9 | 3 | 18 | 23 | 47 | 4.41% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-09-12.md to see failure details
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(4) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
Build timed out (after 30 minutes). Marking the build as failed.(2) -
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository(7) -
Error: EBUSY: resource busy or locked, rmdir '\\?\C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.637'(6) -
fatal: No rebase in progress?(5) -
ERROR: Step ?Archive the artifacts? failed: no workspace for ...(2) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(2) -
parallel/test-runner-coverage(12) -
parallel/test-runner-coverage-thresholds(12) -
parallel/test-runner-output(12) -
parallel/test-http-get-pipeline-problem(7) -
parallel/test-async-context-frame(5) -
parallel/test-http2-large-write-multiple-requests(5) -
parallel/test-http-server-connection-list-when-close(4) -
parallel/test-dns(3) -
parallel/test-runner-watch-mode-complex(3) -
es-module/test-typescript(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 by reading reports/2024-09-12.md and the linked node-test-pull-request runs, then group the listed timeout, workspace, Windows locking, and test failures by cause. Done means the reported recurring CI failures have been addressed and the affected checks no longer fail across pull requests.
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
- 20/100