CI Reliability 2025-01-24
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/64591 to node-test-pull-request/64677 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-01-24.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-01-24 00:10 | 10 | 7 | 8 | 23 | 52 | 10.45% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-01-24.md to see failure details
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(2) -
fatal: No rebase in progress?(8) -
Error: invalid syntax(5) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj](2) -
parallel/test-permission-fs-read(16) -
parallel/test-permission-fs-write(16) -
parallel/test-tls-dhe(12) -
parallel/test-fs-cp(10) -
parallel/test-net-write-fully-async-hex-string(7) -
parallel/test-permission-dc-worker-threads(6) -
parallel/test-runner-module-mocking(6) -
parallel/test-net-write-fully-async-buffer(5) -
node-api/test_threadsafe_function/test(3) -
parallel/test-buffer-tostring-range(3) -
parallel/test-buffer-tostring-rangeerror(3) -
parallel/test-cluster-concurrent-disconnect(3) -
parallel/test-cluster-disconnect-unshared-tcp(3) -
parallel/test-without-async-context-frame(3) -
sequential/test-tls-session-timeout(3) -
es-module/test-esm-loader-entry-url(2) -
parallel/test-file-write-stream4(2) -
parallel/test-icu-env(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-01-24.md and the linked node-test-pull-request runs; use the listed failure messages and test names to identify which failures reproduce. Check the relevant CI jobs and tests, then resolve the tracked failures and update the Progress checklist when the affected PRs pass reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100