CI Reliability 2024-12-14
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/63951 to node-test-pull-request/64047 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-12-14.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-12-14 00:10 | 2 | 16 | 18 | 6 | 58 | 17.39% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-12-14.md to see failure details
Progress
-
parallel/test-abortsignal-drop-settled-signals(17) -
sequential/test-http-server-request-timeouts-mixed(16) -
parallel/test-file-write-stream4(7) -
parallel/test-watch-file-shared-dependency(7) -
parallel/test-net-write-fully-async-buffer(5) -
parallel/test-module-loading-globalpaths(4) -
pummel/test-hash-seed(4) -
parallel/test-child-process-fork-exec-path(3) -
parallel/test-http-chunk-problem(3) -
parallel/test-http-response-status-message(3) -
es-module/test-wasm-web-api(2) -
node-api/test_threadsafe_function/test(2) -
parallel/test-find-package-json(2) -
parallel/test-stream-readable-unpipe-resume(2) -
sequential/test-tls-session-timeout(2) -
Failed to create a temp file on /Users/iojs/build/workspace/node-test-commit-osx/nodes/osx11-x64(2) -
fatal: No rebase in progress?(5) -
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository(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 linked reliability report and the listed CI failures, especially the tests that failed most often. Trace each failure from its CI job output and mark the corresponding Progress item complete once the underlying failure is resolved or separately tracked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, 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
- 25/100