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

未关闭
  • 哪里不对？
#4,247 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
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 分钟
30 天内合并 PR
650

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

callstack/agent-device 的其他 Issue

查看 callstack/agent-device 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。