CI Reliability 2025-02-14
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/65095 to node-test-pull-request/65191 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-02-14.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-02-14 00:09 | 3 | 18 | 10 | 9 | 60 | 20.45% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-02-14.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(7) -
sh: line 9: [: -gt: unary operator expected(7) -
fatal: detected dubious ownership in repository at 'C:/workspace/node-test-binary-windows-native-suites/build'(5) -
fatal: No rebase in progress?(4) -
error: remote GitHub already exists.(2) -
parallel/test-assert-fail(14) -
parallel/test-runner-run-watch(10) -
benchmark/test-benchmark-http2(6) -
parallel/test-file-write-stream4(6) -
parallel/test-buffer-tostring-rangeerror(4) -
parallel/test-net-write-fully-async-buffer(3) -
sequential/test-perf-hooks(3) -
parallel/test-net-write-fully-async-hex-string(2) -
sequential/test-gc-http-client(2) -
sequential/test-tls-session-timeout(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 with reports/2025-02-14.md and the linked node-test-pull-request builds to inspect the listed failure details. Review the repeated timeout, shell, Git, and test failures, then use the report to determine which failures remain reproducible. Done means the tracked CI failures have been addressed and the affected jobs no longer fail repeatedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100