CI Reliability 2024-09-08
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/62045 to node-test-pull-request/62103 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-09-08.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-09-08 00:10 | 22 | 0 | 5 | 42 | 31 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-09-08.md to see failure details
Progress
-
Failed to create a temp file on /Users/iojs/build/workspace/node-test-commit-osx/nodes/osx11-x64(8) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
parallel/test-module-loading-globalpaths(8) -
parallel/test-child-process-spawn-windows-batch-file(7) -
parallel/test-cli-bad-options(7) -
parallel/test-cli-node-options(7) -
parallel/test-cli-permission-deny-fs(7) -
parallel/test-macos-app-sandbox(7) -
parallel/test-async-context-frame(6) -
parallel/test-child-process-fork-exec-path(5) -
parallel/test-file-write-stream4(5) -
parallel/test-esm-loader-hooks-inspect-wait(3) -
parallel/test-runner-run-watch(3) -
parallel/test-runner-watch-mode-complex(3) -
sequential/test-single-executable-application-empty(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-08.md and the linked node-test-pull-request jobs, using the listed failure names to identify which failures are reproducible. Review the ncu-ci walk pr --stats=true --markdown command output and investigate the affected CI jobs; done means the recurring failures are addressed and the relevant pull requests can complete reliably.
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