nodejs / nodejs/reliability

CI Reliability 2025-02-06

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2025-02-06 00:09 4 22 10 13 51 26.51%

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

Progress
  • Error: list index out of range (6)
  • fatal: No rebase in progress? (5)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
  • Error: - process terminated with status 1, expected 0 (2)
  • Failed to trigger sub builds (2)
  • error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj] (2)
  • parallel/test-assert-fail (10)
  • parallel/test-runner-run-watch (8)
  • parallel/test-file-write-stream4 (6)
  • parallel/test-net-write-fully-async-buffer (6)
  • sequential/test-perf-hooks (3)
  • es-module/test-esm-loader-entry-url (2)
  • node-api/test_threadsafe_function/test (2)
  • parallel/test-child-process-cwd (2)
  • parallel/test-net-write-fully-async-hex-string (2)
  • parallel/test-node-output-eval (2)
  • parallel/test-without-async-context-frame (2)
  • sequential/test-tls-session-timeout (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-02-06.md, linked from the issue, and inspect the failure entries generated by ncu-ci walk pr --stats=true --markdown reports/2025-02-06.md. Use the listed failing tests and CI errors as entry points; done means addressing the repeated failures and confirming the affected PR jobs are reliable.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.