Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

iOS smoke lane: preflight 'prepare ios-runner' fails job with daemon_startup_failed on PR lanes (untracked third class)

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

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

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

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
github-actions, typescript
領域
ci-cd, mobile

調査の方向性

Start by reading the ios.yml Smoke Tests preflight step and the daemon startup and cleanup paths reached by pnpm clean:daemon and prepare ios-runner; inspect the lock and daemon.json handling and startup probe. Compare the reported failures with the Windows daemon changes in #3330, then use the existing smoke lane to validate the identified cause. Done means the root cause is established and the preflight no longer fails spuriously.

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

説明

Why

ios.yml Smoke Tests fails at the step "Preflight iOS runner through public CLI" (pnpm clean:daemon + node src/bin.ts prepare ios-runner …) before any scenario runs, with the daemon client's typed details.kind: "daemon_startup_failed":

"message": "Failed to start daemon",
"details": { "kind": "daemon_startup_failed", "startupTimeoutMs": 15000, "startupAttempts": 1, … }

This is a third red class in the iOS smoke lane beyond the two in #3337, and it is exactly the "red that means nothing" problem #2491 / #3336 are about: the step fails the whole job while the diff cannot have caused it.

Evidence (PR-lane only; no failing main run observed)

  • Run 37839500279 (PR #3336, head ffd575ae7, test-only diff — zero files under src/daemon or packages/host-kit), failed 2026-10-08T20:32:31Z.
  • Run 37832908816 (PR #3330 fix/windows-daemon-start-3291, head 0743ddba0), failed the IDENTICAL step with the IDENTICAL details.kind at 2026-10-08T19:38:37Z — different branch, different author, same environment signature within an hour.
  • main shows no failing ios.yml runs on 2026-10-08, so this is currently PR-lane-only evidence.

Both payloads show stateDir/lockPath/infoPath inside the workspace .tmp/agent-device-state, startupTimeoutMs: 15000, startupAttempts: 1, and the client hint pointing at stale lock/daemon metadata from a previous owner in that state directory.

Scope

Find the root owner: whether the preflight's clean:daemon can leave (or collide with) lock/daemon.json state that makes the next start unrecoverable within the 15 s one-attempt budget on shared CI hosts, or whether the startup probe itself is under-budgeted under host load. Note the failing runs overlapped PR #3330, which is actively changing daemon startup on Windows (#3291) — rule that interaction in or out before assuming pure environment flake. Not requested here: re-running lanes to mask it — the re-run of 37839500279 is recorded on #3336.

Related: #2491 (lane signal), #3337 (other untracked smoke-lane signatures).

主要言語
TypeScript
スター
4.9k
フォーク
328
平均マージ
12時間 18分
マージ済み PR（30日）
538

環境構築

はじめの一歩

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

callstack/agent-device のほかの issue

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

似ている issue

TypeScript の issue をもっと見る

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

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