CI Reliability 2024-09-04
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/61790 to node-test-pull-request/61886 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-09-04.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-09-04 00:09 | 7 | 1 | 0 | 35 | 57 | 1.72% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-09-04.md to see failure details
Progress
-
Failed to create a temp file on /Users/iojs/build/workspace/node-test-commit-osx/nodes/osx11-x64(17) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
fatal: No rebase in progress?(19) -
Error: - process terminated with status 1, expected 0(7) -
Failed to trigger node-test-commit(2) -
parallel/test-async-context-frame(12) -
parallel/test-macos-app-sandbox(9) -
parallel/test-runner-watch-mode-complex(8) -
pummel/test-fs-readfile-tostring-fail(8) -
parallel/test-module-loading-globalpaths(7) -
parallel/test-http2-socket-close(6) -
parallel/test-child-process-fork-exec-path(5) -
parallel/test-file-write-stream4(5) -
parallel/test-runner-run-watch(5) -
parallel/test-child-process-spawn-windows-batch-file(4) -
parallel/test-cli-node-options(4) -
parallel/test-cli-permission-deny-fs(4) -
parallel/test-cluster-advanced-serialization(4) -
sequential/test-http-server-request-timeouts-mixed(3) -
sequential/test-single-executable-application-empty(3) -
parallel/test-debugger-heap-profiler(2) -
parallel/test-esm-loader-hooks-inspect-wait(2) -
parallel/test-runner-coverage(2) -
parallel/test-sqlite-statement-sync(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-09-04.md and the linked node-test-pull-request jobs, then review the listed failures and their affected test names. The issue does not identify a target file or specific fix; completion would require investigating the reported CI failures and addressing the causes so the corresponding failures no longer recur.
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