CI Reliability 2024-09-01
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/61665 to node-test-pull-request/61759 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-09-01.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-09-01 00:11 | 4 | 3 | 13 | 10 | 70 | 3.49% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-09-01.md to see failure details
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
fatal: No rebase in progress?(5) -
fatal error: Killed signal terminated program cc1plus(2) -
fatal error: v8-sandbox.h: No such file or directory(2) -
Unknown(2) -
parallel/test-http2-socket-close(15) -
pummel/test-fs-readfile-tostring-fail(14) -
parallel/test-esm-loader-hooks-inspect-wait(10) -
parallel/test-runner-run-watch(9) -
parallel/test-runner-watch-mode-complex(6) -
parallel/test-async-context-frame(4) -
parallel/test-file-write-stream4(4) -
parallel/test-macos-app-sandbox(3) -
parallel/test-runner-output(3) -
parallel/test-sqlite-statement-sync(3) -
parallel/test-performance-function(2) -
parallel/test-runner-coverage(2) -
parallel/test-runner-coverage-thresholds(2) -
parallel/test-worker-nearheaplimit-deadlock(2) -
sequential/test-http-server-request-timeouts-mixed(2) -
wpt/test-timers(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 reports/2024-09-01.md and the failures linked from node-test-pull-request/61665 through 61759; the report was generated with ncu-ci walk pr --stats=true --markdown reports/2024-09-01.md. Investigate the listed CI and test failures, then use the Progress checklist to track which failure categories have been addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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