nodejs / nodejs/reliability

CI Reliability 2024-10-09

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2024-10-09 00:09 0 21 16 3 60 21.65%

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

Progress
  • es-module/test-loaders-workers-spawned (7)
  • node-api/test_threadsafe_function/test (6)
  • parallel/test-stream-readable-unpipe-resume (6)
  • sequential/test-http-server-request-timeouts-mixed (6)
  • parallel/test-net-write-fully-async-buffer (4)
  • wpt/test-compression (4)
  • parallel/test-async-context-frame (3)
  • pummel/test-heapdump-shadow-realm (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 (4)
  • fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository (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/2024-10-09.md and the linked CI runs from node-test-pull-request/62898 through 62997. Review the listed failure entries, beginning with the tests that failed most often, and trace each to its relevant test or CI behavior. Done means the reported failures have been investigated and the corresponding progress entries can be resolved with CI evidence.

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.