nodejs / nodejs/reliability

CI Reliability 2024-11-29

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2024-11-29 00:10 2 13 24 3 58 13.68%

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

Progress
  • sequential/test-http-server-request-timeouts-mixed (11)
  • parallel/test-watch-file-shared-dependency (7)
  • parallel/test-file-write-stream4 (6)
  • parallel/test-net-write-fully-async-buffer (5)
  • parallel/test-stream-readable-unpipe-resume (5)
  • es-module/test-esm-loader-entry-url (2)
  • parallel/test-buffer-tostring-rangeerror (2)
  • parallel/test-esm-loader-hooks-inspect-brk (2)
  • parallel/test-http-response-status-message (2)
  • parallel/test-without-async-context-frame (2)
  • sequential/test-tls-session-timeout (2)
  • wpt/test-compression (2)
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (2)
  • Build timed out (after 60 minutes). Marking the build as failed. (2)
  • fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository (3)
  • fatal: No rebase in progress? (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/2024-11-29.md and the CI runs linked in the issue, covering node-test-pull-request/63660 through 63756. Review the listed failing tests and infrastructure errors, then use the generated ncu-ci command context to investigate them; done means the checklist items are addressed and the CI failure patterns no longer recur.

Written by the indexing model from the issue text.

Assessment

Tech stack
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.