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

オープン
  • 何か問題がありますか？
#4,247 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
55/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
github-actions, typescript
領域
ci-cd, testing-qa

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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).

主要言語
TypeScript
スター
5.3k
フォーク
377
平均マージ
14時間 6分
マージ済み PR（30日）
650

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

callstack/agent-device のほかの issue

callstack/agent-device の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。