nodejs / nodejs/reliability

CI Reliability 2025-06-05

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2025-06-05 00:11 0 14 29 3 54 14.43%

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

Progress
  • sequential/test-performance-eventloopdelay (7)
  • async-hooks/test-improper-order (3)
  • parallel/test-stream-readable-to-web (3)
  • parallel/test-performance-eventlooputil (2)
  • parallel/test-runner-run-watch (2)
  • sequential/test-tls-session-timeout (2)
  • wpt/test-streams (2)
  • Build timed out (after 30 minutes). Marking the build as failed. (3)
  • Build timed out (after 60 minutes). Marking the build as failed. (2)
  • ERROR: Error fetching remote repo 'origin' (3)
  • fatal: No rebase in progress? (3)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
  • Failed to trigger node-test-commit (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-06-05.md and the linked node-test-pull-request jobs to review the listed failures, including the named test cases, timeouts, repository fetch errors, and trigger failures. Trace each failure to its CI job or test entry; done means the reported recurring failures have been investigated and the relevant CI runs no longer reproduce them.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.