nodejs / nodejs/reliability

CI Reliability 2024-12-29

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2024-12-29 00:11 1 10 21 0 68 10.10%

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

Progress
  • ERROR: Error fetching remote repo 'origin' (2)
  • 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 sub builds (2)
  • sequential/test-http-server-request-timeouts-mixed (15)
  • es-module/test-wasm-web-api (5)
  • sequential/test-worker-prof (5)
  • parallel/test-file-write-stream4 (4)
  • parallel/test-watch-file-shared-dependency (3)
  • parallel/test-abortsignal-drop-settled-signals (2)
  • parallel/test-buffer-tostring-rangeerror (2)
  • parallel/test-fs-stat-bigint (2)
  • parallel/test-http-chunk-problem (2)
  • parallel/test-net-write-fully-async-buffer (2)
  • sequential/test-perf-hooks (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 by reading the linked reports/2024-12-29.md failure details and the Jenkins runs from node-test-pull-request/64146 through 64243. Review the listed CI errors and failing tests to determine which failure is actionable; done is not defined beyond addressing the tracked reliability failures.

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
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.