CI Reliability 2024-12-19
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/64010 to node-test-pull-request/64099 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-12-19.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-12-19 00:10 | 8 | 15 | 12 | 16 | 49 | 19.74% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-12-19.md to see failure details
Progress
-
sequential/test-http-server-request-timeouts-mixed(12) -
parallel/test-watch-file-shared-dependency(10) -
parallel/test-abortsignal-drop-settled-signals(4) -
parallel/test-module-loading-globalpaths(4) -
parallel/test-net-write-fully-async-buffer(4) -
parallel/test-child-process-fork-exec-path(3) -
parallel/test-file-write-stream4(3) -
parallel/test-stream-readable-unpipe-resume(3) -
node-api/test_worker_buffer_callback/test-free-called(2) -
parallel/test-find-package-json(2) -
parallel/test-http-chunk-problem(2) -
parallel/test-without-async-context-frame(2) -
pummel/test-hash-seed(2) -
sequential/test-worker-prof(2) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(8) -
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 reports/2024-12-19.md and the linked CI jobs, then investigate the listed failing tests such as sequential/test-http-server-request-timeouts-mixed and parallel/test-watch-file-shared-dependency. Done means the reported CI failures and configuration errors are resolved and the affected pull requests produce reliable green results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100