nodejs / nodejs/reliability

CI Reliability 2025-12-25

Open
#1,412 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/70504 to node-test-pull-request/70600 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-12-25.md)

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2025-12-25 00:12 1 10 28 1 60 10.20%

Open https://github.com/nodejs/reliability/blob/main/reports/2025-12-25.md to see failure details

Progress
  • parallel/test-repl-programmatic-history (6)
  • parallel/test-quic-test-client (5)
  • sequential/test-performance-eventloopdelay (5)
  • test-runner/test-run-watch-without-file (4)
  • wpt/test-hr-time (4)
  • async-hooks/test-improper-order (3)
  • test-runner/test-run-watch-run-duration (3)
  • async-hooks/test-emit-after-on-destroyed (2)
  • test-runner/test-run-watch-dependency-repeatedly (2)
  • Build timed out (after 60 minutes). Marking the build as failed. (3)
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (2)
  • Build timed out (after 30 minutes). Marking the build as failed. (2)
  • ERROR: Error fetching remote repo 'origin' (9)
  • Failed to trigger node-test-commit (3)
  • ERROR: Step �Archive the artifacts� failed: no workspace for ... (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/2025-12-25.md and the linked node-test-pull-request runs, then review the listed test and infrastructure failures. Use the generated ncu-ci walk command and the individual failure details to reproduce issues; done means resolving the applicable failures and checking off the corresponding progress entries.

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
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.