CI Reliability 2024-09-28
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/62713 to node-test-pull-request/62808 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-09-28.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-09-28 00:10 | 3 | 23 | 18 | 3 | 53 | 24.47% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-09-28.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(3) -
Error: invalid syntax(8) -
fatal: No rebase in progress?(5) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
node-api/test_threadsafe_function/test(6) -
parallel/test-http-get-pipeline-problem(4) -
parallel/test-http2-large-write-multiple-requests(4) -
parallel/test-net-write-fully-async-buffer(4) -
parallel/test-stream-readable-unpipe-resume(3) -
es-module/test-esm-child-process-fork-main(2) -
parallel/test-async-context-frame(2) -
parallel/test-child-process-disconnect(2) -
parallel/test-child-process-fork(2) -
parallel/test-child-process-fork-closed-channel-segfault(2) -
parallel/test-child-process-fork-getconnections(2) -
parallel/test-child-process-fork-net(2) -
parallel/test-child-process-fork-net-server(2) -
parallel/test-child-process-fork-net-socket(2) -
parallel/test-child-process-fork-stdio-string-variant(2) -
parallel/test-child-process-http-socket-leak(2) -
parallel/test-child-process-ipc-next-tick(2) -
parallel/test-child-process-send-keep-open(2) -
parallel/test-child-process-send-returns-boolean(2) -
parallel/test-cluster-accept-fail(2) -
parallel/test-cluster-bind-twice(2) -
parallel/test-cluster-concurrent-disconnect(2) -
parallel/test-cluster-disconnect(2) -
parallel/test-cluster-disconnect-unshared-tcp(2) -
parallel/test-cluster-eaccess(2) -
parallel/test-cluster-eaddrinuse(2) -
parallel/test-cluster-fork-stdio(2) -
parallel/test-cluster-invalid-message(2) -
parallel/test-cluster-message(2) -
parallel/test-cluster-net-listen-ipv6only-false(2) -
parallel/test-cluster-net-send(2) -
parallel/test-cluster-primary-error(2) -
parallel/test-cluster-primary-kill(2) -
parallel/test-cluster-rr-handle-close(2) -
parallel/test-cluster-rr-handle-keep-loop-alive(2) -
parallel/test-cluster-rr-handle-ref-unref(2) -
parallel/test-cluster-send-deadlock(2) -
parallel/test-cluster-send-handle-twice(2) -
parallel/test-cluster-server-restart-none(2) -
parallel/test-cluster-server-restart-rr(2) -
parallel/test-cluster-shared-leak(2) -
parallel/test-cluster-worker-disconnect-on-error(2) -
parallel/test-cluster-worker-handle-close(2) -
parallel/test-cluster-worker-no-exit(2) -
parallel/test-cluster-worker-wait-server-close(2) -
parallel/test-dgram-exclusive-implicit-bind(2) -
parallel/test-fs-rmdir-recursive-sync-warns-on-file(2) -
parallel/test-fs-rmdir-recursive-throws-on-file(2) -
parallel/test-fs-rmdir-recursive-warns-on-file(2) -
parallel/test-inspector-open(2) -
parallel/test-net-child-process-connect-reset(2) -
parallel/test-net-listen-exclusive-random-ports(2) -
parallel/test-net-listen-twice(2) -
parallel/test-net-server-close-before-ipc-response(2) -
parallel/test-runner-output(2) -
parallel/test-stdout-close-catch(2) -
parallel/test-tls-ticket-cluster(2) -
sequential/test-child-process-pass-fd(2) -
sequential/test-cluster-net-listen-ipv6only-none(2) -
sequential/test-cluster-net-listen-ipv6only-rr(2) -
sequential/test-cluster-send-handle-large-payload(2) -
sequential/test-inspector-open-dispose(2) -
sequential/test-net-listen-shared-ports(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-28.md and the linked node-test-pull-request runs, using the listed failure categories and test names to trace recurring failures. Done means identifying and addressing the reported CI reliability failures so the affected checks no longer fail repeatedly.
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