nodejs / nodejs/reliability

CI Reliability 2025-05-29

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2025-05-29 00:11 0 19 18 1 62 19.19%

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

Progress
  • Build timed out (after 30 minutes). Marking the build as failed. (3)
  • Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): error=0, Failed to exec spawn helper: pid: 3306322, exit value: 1 (2)
  • ERROR: Error fetching remote repo 'origin' (2)
  • fatal: No rebase in progress? (3)
  • parallel/test-http2-debug (20)
  • parallel/test-buffer-tostring-range (8)
  • pummel/test-blob-slice-with-large-size (8)
  • async-hooks/test-improper-unwind (3)
  • parallel/test-runner-run-watch (3)
  • parallel/test-zlib-brotli-16GB (3)
  • sequential/test-performance-eventloopdelay (3)
  • wpt/test-streams (3)

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-05-29.md and the linked node-test-pull-request jobs to inspect details for each repeated failure. Triage the listed infrastructure and test failures, then verify that the affected CI runs no longer reproduce them; the issue provides no specific source files or tests beyond the named test paths.

Written by the indexing model from the issue text.

Assessment

Tech stack
nodejs, shell
Domain
ci-cd, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.