CI Reliability 2025-01-30
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/64737 to node-test-pull-request/64831 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-01-30.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-01-30 00:09 | 2 | 15 | 23 | 4 | 56 | 15.96% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-01-30.md to see failure details
Progress
-
parallel/test-permission-fs-read(17) -
parallel/test-permission-fs-write(17) -
parallel/test-fs-cp(11) -
parallel/test-net-write-fully-async-hex-string(6) -
parallel/test-file-write-stream4(4) -
parallel/test-watch-mode-files_watcher(3) -
es-module/test-wasm-web-api(2) -
parallel/test-buffer-tostring-rangeerror(2) -
parallel/test-cluster-fork-stdio(2) -
parallel/test-esm-loader-hooks-inspect-wait(2) -
parallel/test-fs-watch-recursive-add-file-with-url(2) -
parallel/test-net-write-fully-async-buffer(2) -
parallel/test-runner-output(2) -
parallel/test-stream-readable-unpipe-resume(2) -
parallel/test-without-async-context-frame(2) -
parallel/test-zlib-brotli-16GB(2) -
wpt/test-timers(2) -
Build timed out (after 30 minutes). Marking the build as failed.(4) -
sh: line 12: [: -gt: unary operator expected(2) -
Unknown(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
Open reports/2025-01-30.md for the failure details, then use the linked CI jobs and the listed test names as entry points. Triage the repeated failures, including parallel/test-permission-fs-read and parallel/test-fs-cp, and verify that the affected CI jobs no longer reproduce them.
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
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100