nodejs / nodejs/reliability

CI Reliability 2024-09-19

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2024-09-19 00:09 3 20 17 2 58 21.05%

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

Progress
  • ERROR: Error fetching remote repo 'origin' (4)
  • Failed to trigger fanned build (16)
  • fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository (7)
  • parallel/test-cli-node-options (4)
  • parallel/test-cli-permission-deny-fs (4)
  • parallel/test-http2-large-write-multiple-requests (4)
  • node-api/test_threadsafe_function/test (3)
  • parallel/test-http-remove-header-stays-removed (2)
  • parallel/test-runner-no-isolation-hooks (2)
  • parallel/test-runner-watch-mode-complex (2)
  • pummel/test-hash-seed (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-09-19.md and the linked CI runs from node-test-pull-request/62444 through 62540. Review the failure details for each unchecked Progress item, beginning with the repeated remote-repository and fanned-build failures. Done means the listed recurring failures have been investigated and the corresponding Progress items can be checked.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, shell
Domain
ci-cd, devops, testing
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.