CI Coverage job dies silently on about a third of PR runs since the Blacksmith migration

Ouverte
  • Quelque chose ne va pas ?
#4,247 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
55/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
github-actions, typescript
Domaine
ci-cd, testing-qa

Piste de recherche

Start with the Coverage job workflow and its Run coverage step, then inspect the runner logs for the example job and compare memory use across successful and failed runs. Identify whether the process is killed and capture a useful cause, such as the signal or last test file; if memory is the cause, choose a runner or worker configuration based on measurements. Done means 10 consecutive PR Coverage runs pass or each failure names a failing test, with no skipped tests or reduced coverage threshold.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

bug ready-for-agent

Purpose

The Coverage job in CI dies without reporting a cause on about one PR run in three. Since the Blacksmith runner migration (#4185, 2026-11-03), 11 of the last 38 CI runs that ran Coverage failed it, and the PR diff isn't the cause. For example, #4231 changes only help text and failed it twice, while #4243 passed on its first run.

Current behavior

Example: job 127467430367 on #4231 at 5b9d769.

  • runs-on: blacksmith-4vcpu-ubuntu-2404, timeout-minutes: 30. The job ran 10 minutes, so it did not time out.
  • The Run coverage step prints agent-device: building macOS helper (first run or helper update) four times at 19:12:57. It then prints nothing for about 3.5 minutes, and the step fails at 19:16:18.
  • No test is named as failing, and no Test Files or Tests summary is printed. There is no ELIFECYCLE line and no Process completed with exit code line.
  • The error lines earlier in the log (--iterations must be a positive integer, Unknown option '--not-a-flag', Android helper diagnostics) are expected output from tests of failure paths.

A step that ends with no exit line at all suggests the test process was killed, for example by the out-of-memory killer, not that a test failed.

Required behavior

  • Find out what ends the step, for example from the runner's memory usage or kernel OOM messages, or by running the coverage step with --reporter=verbose and a heap limit.
  • If it is memory, give the Coverage job enough of it: a larger Blacksmith runner, a GitHub-hosted runner, or fewer coverage workers. Choose by measurement.
  • If the process can be killed, the job must print a cause, such as the signal or the last test file, so the next failure names it.

Completion conditions

  • 10 consecutive Coverage runs on PRs pass, or each failure names a failing test.
  • The fix is a workflow or test-runner configuration change. No test is skipped and no coverage threshold is lowered.

Dependencies

Related to #4185 (the Blacksmith migration).

Langage dominant
TypeScript
Étoiles
5.3k
Forks
377
Merge moyen
14 h 6 min
PR mergées (30 j)
650

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de callstack/agent-device

Toutes les issues de callstack/agent-device

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.