CI Reliability 2024-09-06
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/61911 to node-test-pull-request/62021 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-09-06.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-09-06 00:09 | 1 | 5 | 4 | 17 | 73 | 6.10% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-09-06.md to see failure details
Progress
-
Failed to create a temp file on /Users/iojs/build/workspace/node-test-commit-osx/nodes/osx11-x64(19) -
Build timed out (after 60 minutes). Marking the build as failed.(8) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(3) -
Command "git clean -fdx" returned status code 143:(3) -
Error: - process terminated with status 1, expected 0(16) -
fatal: No rebase in progress?(2) -
sequential/test-http-server-request-timeouts-mixed(25) -
parallel/test-async-context-frame(16) -
parallel/test-esm-loader-hooks-inspect-wait(11) -
parallel/test-macos-app-sandbox(11) -
parallel/test-runner-run-watch(11) -
parallel/test-http2-socket-close(8) -
pummel/test-fs-readfile-tostring-fail(8) -
parallel/test-debugger-heap-profiler(5) -
parallel/test-module-loading-globalpaths(5) -
parallel/test-runner-watch-mode-complex(5) -
parallel/test-http-get-pipeline-problem(4) -
parallel/test-file-write-stream4(3) -
sequential/test-single-executable-application-empty(3) -
parallel/test-child-process-fork-exec-path(2) -
parallel/test-performance-function(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-06.md and the linked node-test-pull-request jobs, then inspect the listed failure signatures and named tests such as sequential/test-http-server-request-timeouts-mixed and parallel/test-async-context-frame. Done means the recurring failures identified in this report no longer occur in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, macos, 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