CI Reliability 2024-12-11
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/63893 to node-test-pull-request/63980 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-12-11.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-12-11 00:10 | 9 | 13 | 23 | 11 | 44 | 16.25% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-12-11.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(2) -
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository(2) -
parallel/test-abortsignal-drop-settled-signals(10) -
sequential/test-http-server-request-timeouts-mixed(8) -
parallel/test-http-response-status-message(4) -
pummel/test-hash-seed(4) -
es-module/test-wasm-web-api(3) -
parallel/test-file-write-stream4(3) -
parallel/test-net-write-fully-async-buffer(3) -
parallel/test-watch-file-shared-dependency(3) -
sequential/test-tls-session-timeout(3) -
node-api/test_threadsafe_function/test(2) -
parallel/test-stream-readable-unpipe-resume(2) -
wpt/test-compression(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 the failure details in reports/2024-12-11.md and reviewing the listed CI errors and test names. Investigate the failures from the linked node-test-pull-request runs; done means the recurring failures are addressed and the affected CI tests no longer fail across pull requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, node.js, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100