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

Ouverte
#1,803 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
30/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
ios, typescript
Domaine
devtools

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
TypeScript
Étoiles
705
Forks
40
Merge moyen
12 h 9 min
PR mergées (30 j)
376

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de callstackincubator/simlock

Toutes les issues de callstackincubator/simlock

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.