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

オープン
#1,700 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

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

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

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
43/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
android, typescript
領域
backend, devtools

調査の方向性

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.

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

説明

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.

主要言語
TypeScript
スター
705
フォーク
40
平均マージ
12時間 9分
マージ済み PR(30日)
376

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

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

callstackincubator/simlock のほかの issue

callstackincubator/simlock の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

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

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