nodejs / nodejs/reliability

CI Reliability 2024-10-10

Open
#992 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/62918 to node-test-pull-request/63015 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-10-10.md)

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2024-10-10 00:10 3 18 13 2 64 18.95%

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

Progress
  • node-api/test_threadsafe_function/test (8)
  • sequential/test-http-server-request-timeouts-mixed (8)
  • es-module/test-loaders-workers-spawned (6)
  • wpt/test-compression (5)
  • parallel/test-stream-readable-unpipe-resume (4)
  • parallel/test-net-write-fully-async-buffer (3)
  • parallel/test-async-context-frame (2)
  • pummel/test-heapdump-shadow-realm (2)
  • Build timed out (after 30 minutes). Marking the build as failed. (5)
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (2)
  • ERROR: Error fetching remote repo 'origin' (3)
  • Error: invalid syntax (10)
  • fatal: No rebase in progress? (5)
  • fatal error: Killed signal terminated program cc1plus (3)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
  • ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (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 reports/2024-10-10.md and the linked CI jobs for the listed failures, beginning with one named test such as node-api/test_threadsafe_function/test. Use the generated failure details to identify a focused cause and verify the affected CI jobs no longer reproduce it; the issue is complete when the tracked failures are resolved or clearly accounted for.

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
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.