nodejs / nodejs/reliability

CI Reliability 2025-04-11

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2025-04-11 00:11 0 0 23 2 75 0.00%

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

Progress
  • pummel/test-buffer-large-size (26)
  • parallel/test-repl-custom-eval (12)
  • parallel/test-runner-plan (7)
  • parallel/test-file-write-stream4 (5)
  • parallel/test-crypto-authenticated (3)
  • parallel/test-cluster-fork-stdio (2)
  • parallel/test-http-chunk-problem (2)
  • parallel/test-zlib-convenience-methods (2)
  • sequential/test-performance-eventloopdelay (2)
  • ERROR: Error fetching remote repo 'origin' (3)
  • Error: list index out of range (7)
  • 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

Read the linked reports/2025-04-11.md and inspect the listed failures, starting with the tests that failed most often such as pummel/test-buffer-large-size and parallel/test-repl-custom-eval. Use the report details to identify causes, then mark each Progress item complete when its CI failure is resolved and the affected PRs pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, 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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.