nodejs / nodejs/reliability

CI Reliability 2026-01-05

Open
#1,423 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/70572 to node-test-pull-request/70670 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-01-05.md)

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-01-05 00:13 1 7 32 15 45 8.33%

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

Progress
  • Build timed out (after 30 minutes). Marking the build as failed. (2)
  • ERROR: Error fetching remote repo 'origin' (5)
  • fatal error: too many errors emitted, stopping now [-ferror-limit=] (5)
  • Failed to trigger node-test-commit (4)
  • fatal error: Killed signal terminated program cc1plus (4)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
  • ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (2)
  • parallel/test-repl-programmatic-history (8)
  • parallel/test-quic-test-client (5)
  • test-runner/test-run-watch-run-duration (3)
  • async-hooks/test-improper-order (2)
  • es-module/test-vm-contextified-script-leak (2)
  • parallel/test-zlib-brotli-16GB (2)
  • sequential/test-performance-eventloopdelay (2)
  • wpt/test-webcrypto (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 the linked reliability report and the Jenkins builds from node-test-pull-request/70572 through 70670. Review the listed timeout, repository-fetch, compiler, trigger, and test failures to determine which are actionable. Done means the relevant CI failure causes are identified and addressed, but this issue does not name a target file or test change.

Written by the indexing model from the issue text.

Assessment

Tech stack
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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.