Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#3,342 7 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github-actions, typescript
Ambito
ci-cd, mobile

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
TypeScript
Stelle
4.9k
Fork
328
Merge medio
12h 13m
PR unite (30g)
541

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di callstack/agent-device

Tutte le issue di callstack/agent-device

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.