nodejs / nodejs/reliability

CI Reliability 2025-06-15

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2025-06-15 00:12 1 2 31 8 58 2.20%

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

Progress
  • Build timed out (after 30 minutes). Marking the build as failed. (7)
  • ERROR: Error fetching remote repo 'origin' (3)
  • fatal error: Killed signal terminated program cc1plus (4)
  • Failed to trigger node-test-commit (2)
  • sh: line 12: [: -gt: unary operator expected (2)
  • parallel/test-buffer-tostring-range (10)
  • sequential/test-performance-eventloopdelay (6)
  • parallel/test-config-file (4)
  • parallel/test-stream-readable-to-web (3)
  • parallel/test-without-async-context-frame (3)
  • sequential/test-tls-session-timeout (3)
  • parallel/test-net-autoselectfamily (2)
  • parallel/test-worker-nearheaplimit-deadlock (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

Open reports/2025-06-15.md in the linked reliability repository and compare it with the node-test-pull-request builds 67350–67449. Review the listed timeout, fetch, compiler, trigger, shell, and test failures; the work is done when the repeated failures have been addressed and the affected CI jobs no longer reproduce them.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
ci-cd, devops, testing
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.