Windows: daemon stop times out after 300 s while the warm pool remakes an Android seed (EBUSY on cache.img)

Aperta
#1,700 2 commenti 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
43/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
android, typescript
Ambito
backend, devtools

Direzione di ricerca

Start with the daemon stop path and warm pool seed creation and cleanup; the report identifies those components and the failing cache.img unlink, but gives no file paths or tests. Reproduce on Windows with the Android SDK path changing between ANDROID_HOME and %LOCALAPPDATA%\Android\Sdk, then trace how stop handles an in-progress seed make. Done means stop returns within its bound, cancels the make and stops its emulator, and a locked seed file does not delay shutdown.

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

Descrizione

os:windows platform:android request:new

On Windows, simlock daemon stop failed after 300 s while the warm pool was making an Android seed:

PS> simlock daemon stop
{"error":{"code":"SERVICE_FAILED","message":"The running daemon did not stop within 300 s."}}

The daemon log shows the stop asked at 08:26:07 and the daemon stopping only after the seed make failed, about 300 s later:

{"timestamp":1794990367512,"level":"info","module":"daemon.server","message":"Daemon stopping","fields":{"reason":"requested"}}
{"timestamp":1794990669562,"level":"warn","module":"daemon.warm-pool","message":"warm pool creation of a device failed","fields":{"model":"Pixel 9","step":"provision","error":"Error: EBUSY: resource busy or locked, unlink 'D:\\sv\\spec1071\\devices\\android\\sources\\seed_5008dc0e-62bc-41bc-9231-0678b6f62474\\simlock.avd\\cache.img'"}}
{"timestamp":1794990670759,"level":"info","module":"daemon.server","message":"Daemon stopped","fields":{"reason":"requested"}}

A simlock daemon start 35 s later worked.

How it got there: the worker had been started with ANDROID_HOME=D:\Android\Sdk, then restarted with ANDROID_HOME and ANDROID_SDK_ROOT unset and the SDK found at %LOCALAPPDATA%\Android\Sdk (a junction to the same folder). The warm pool then remade the Pixel 9 / API 35 seed, and the stop came during that make. Two things look wrong:

  1. The stop waited for the seed make. It did not give up on the make or stop its emulator.
  2. Removing the old seed's cache.img failed with EBUSY. A process still had the file open.

Seen on Windows 11 23H2 (DesktopWindows), main at 2df19f881, emulator 37.2.13, while specifying #1692. Not checked on macOS or Linux.

Expected

simlock daemon stop returns within its bound while a seed is being made: the make is cancelled and its emulator stopped. A seed whose files are held open is refused or retried, and does not hold up the stop.

Part of #1068.

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.