iOS: destroy stops at a timed-out simctl shutdown, so quarantine never reaches simctl delete

Aperta
#1,803 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
30/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
ios, typescript
Ambito
devtools

Direzione di ricerca

Start in src/drivers/ios/simctl.ts around line 64, where shutdown uses COMMAND_TIMEOUT_MS, then read destroy in src/drivers/ios/index.ts near lines 449-452. The retry and give-up calls are in src/core/quarantine-coordinator.ts at lines 313 and 367. The open question is whether simctl delete succeeds while a shutdown is unfinished; answer it on a real simulator before changing the code. Done means a timed-out shutdown no longer blocks the delete, or a setting exists for the shutdown timeout.

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

Descrizione

bug:new

A simulator whose simctl shutdown keeps running past 30 s is never deleted at lease end, in quarantine or at give-up, because the iOS destroy stops at the shutdown.

  • src/drivers/ios/simctl.ts:64: shutdown waits a fixed COMMAND_TIMEOUT_MS (30 s), and throws simctl shutdown <udid> timed out after 30000ms at the limit. No setting changes it (#1563 added ios.simulator.createTimeoutMs for clone/create only).
  • src/drivers/ios/index.ts:449-452: destroy runs shutdown and then simctl delete. A shutdown that times out throws before delete is tried.
  • src/core/quarantine-coordinator.ts:313 (each retry) and :367 (give-up) both call that destroy. On a host where the shutdown keeps timing out (memory pressure, swap ~2.5 GB in #1801), each attempt spends 30 s on the shutdown and none reaches the delete. The device ends device.quarantine-stranded, keeping its capacity slot and its disk until an operator acts.

The record is kept, so this leaves no orphan. #1801 showed the log lines but not this end state.

Open question for the fix, to settle on a real simulator: does simctl delete remove a simulator whose shutdown has not finished? If it does, destroy can go on to the delete after a timed-out shutdown. If not, the shutdown needs a setting like createTimeoutMs.

Found while triaging #1801.

Written by an agent.

Lingua principale
TypeScript
Stelle
705
Fork
40
Merge medio
12h 9m
PR unite (30g)
376

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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 callstackincubator/simlock

Tutte le issue di callstackincubator/simlock

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.