nodejs / nodejs/reliability

CI Reliability 2026-03-26

Open
#1,491 0 comments 0 reactions 0 assignees View on GitHub

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/71845 to node-test-pull-request/71944 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-03-26.md)

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-03-26 00:19 0 10 6 12 72 11.36%

Open https://github.com/nodejs/reliability/blob/main/reports/2026-03-26.md to see failure details

Progress
  • sequential/test-performance-eventloopdelay (5)
  • parallel/test-debugger-heap-profiler (4)
  • client-proxy/test-http-proxy-request-invalid-char-in-url (2)
  • client-proxy/test-https-proxy-request-empty-response (2)
  • client-proxy/test-https-proxy-request-invalid-char-in-url (2)
  • parallel/test-child-process-advanced-serialization-splitted-length-field (2)
  • parallel/test-child-process-constructor (2)
  • parallel/test-http-agent-keep-alive-timeout-buffer (2)
  • parallel/test-http-expect-continue (2)
  • parallel/test-http2-dont-lose-data (2)
  • parallel/test-runner-run-watch (2)
  • parallel/test-runner-watch-mode (2)
  • parallel/test-watch-mode-files_watcher (2)
  • test-runner/test-run-watch-without-file (2)
  • wasi/test-wasi-poll (2)
  • Failed to trigger node-test-commit (8)
  • fatal: No rebase in progress? (3)
  • Error: 'utf-8' codec can't decode byte 0xa6 in position 245: invalid start byte (2)
  • Failed to trigger fanned build (2)
  • Failed to trigger sub builds (2)
  • fatal error: Killed signal terminated program cc1plus (2)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with reports/2026-03-26.md and the linked CI runs from node-test-pull-request/71845 through 71944. Review the listed test and infrastructure failures, beginning with one repeated failure and its corresponding run details. Done means the selected failures are investigated and the relevant CI failures are resolved or clearly tracked.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, nodejs, 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
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.