CI Reliability 2024-12-17
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/63969 to node-test-pull-request/64070 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-12-17.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-12-17 00:11 | 1 | 15 | 19 | 9 | 56 | 16.67% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-12-17.md to see failure details
Progress
-
sequential/test-http-server-request-timeouts-mixed(14) -
parallel/test-abortsignal-drop-settled-signals(11) -
parallel/test-watch-file-shared-dependency(9) -
parallel/test-file-write-stream4(6) -
parallel/test-module-loading-globalpaths(4) -
parallel/test-net-write-fully-async-buffer(4) -
parallel/test-child-process-fork-exec-path(3) -
parallel/test-http-chunk-problem(3) -
parallel/test-stream-readable-unpipe-resume(3) -
pummel/test-hash-seed(3) -
es-module/test-wasm-web-api(2) -
node-api/test_threadsafe_function/test(2) -
parallel/test-find-package-json(2) -
sequential/test-worker-prof(2) -
fatal: No rebase in progress?(4) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
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 for the node-test-pull-request runs and inspect the listed failing tests, including sequential/test-http-server-request-timeouts-mixed and parallel/test-abortsignal-drop-settled-signals. Reproduce failures using the project’s CI test entry points and determine which listed failures remain. Done means the recurring failures are addressed and the progress checklist is updated.
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
- 25/100