CI Reliability 2026-03-27
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/71957 to node-test-pull-request/72053 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-03-27.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-03-27 00:18 | 2 | 7 | 2 | 1 | 88 | 7.22% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-03-27.md to see failure details
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(2) -
ERROR: Error fetching remote repo 'origin'(2) -
sh: line 1: 429:: command not found(7) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(5) -
error: remote GitHub already exists.(2) -
fatal: No rebase in progress?(2) -
Unknown(16) -
sequential/test-fs-watch(10) -
parallel/test-fs-watch-recursive-delete(5) -
parallel/test-debugger-heap-profiler(3) -
parallel/test-http-res-write-after-end(3) -
sequential/test-watch-mode-watch-flags(3) -
client-proxy/test-http-proxy-request-no-proxy(2) -
client-proxy/test-http-proxy-request-socket-keep-alive(2) -
client-proxy/test-http-request-proxy-post-server-failure(2) -
client-proxy/test-http-set-global-proxy-from-env-fetch-https(2) -
client-proxy/test-https-proxy-fetch(2) -
client-proxy/test-https-proxy-request-https-proxy(2) -
es-module/test-vm-contextified-script-leak(2) -
parallel/test-debugger-clear-breakpoints(2) -
parallel/test-http-aborted(2) -
parallel/test-http-agent-timeout(2) -
parallel/test-http-client-reject-cr-no-lf(2) -
parallel/test-http-outgoing-destroyed(2) -
parallel/test-http-upgrade-binary(2) -
parallel/test-http2-options-max-reserved-streams(2) -
parallel/test-http2-respond-file-fd-invalid(2) -
parallel/test-https-agent-servername(2) -
parallel/test-https-max-headers-count(2) -
parallel/test-inspector-scriptparsed-context(2) -
parallel/test-net-write-fully-async-buffer(2) -
parallel/test-watch-mode-files_watcher(2) -
pummel/test-fs-watch-non-recursive(2) -
sequential/test-watch-mode-restart-esm-loading-error(2) -
test-runner/test-run-watch-dependency-repeatedly(2) -
wpt/test-blob(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/2026-03-27.md and the linked Jenkins runs from node-test-pull-request/71957 through 72053. Use the listed ncu-ci command and Progress entries to investigate the repeated CI failures; done means the relevant failure causes are addressed and the affected checks no longer recur.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100