On this machine (Windows + AEHD hypervisor), Gradle Managed Device instrumented tasks (apiXXDebugAndroidTest) fail during setup: GMD's emulator snapshot creation times out (AvdSnapshotHandler$EmulatorSnapshotCannotCreatedException, retries 5x, each reboot = the 'cycling' we chased for hours). The emulator itself boots fine (verified: 8GB RAM, boot_completed=1, shell-responsive) — only GMD's snapshot step is broken. Root cause: AEHD 2.2 can't complete the snapshot save/load (also caused the earlier -check-snapshot-loadable hangs).
Scope
All LOCAL GMD instrumented tasks: coverage lane 3 (#248), lane 5 (#250), AND the /preflight api35/api36 steps (GMD tasks added in #266) — so preflight as designed fails locally on this box. GMD-specific: CI is unaffected (it uses reactivecircus/android-emulator-runner + connectedDebugAndroidTest, no GMD).
Fix
Use connectedDebugAndroidTest against a manually-provisioned emulator (cold boot, -no-snapshot) for local instrumented tests — same technique as .claude/skills/preflight/api37_e2e.py and CI. Generalize that api37 script to any API level and switch the preflight api35/api36 steps (and local coverage-lane validation) to it. (Optionally investigate disabling GMD snapshots / bumping setupTimeout, but connectedDebugAndroidTest is the known-reliable path.)
DoD
Preflight runs api35/36/37 locally via connectedDebugAndroidTest (no GMD), green on this machine; the AEHD/GMD-snapshot limitation documented.
## Finding
On this machine (Windows + AEHD hypervisor), Gradle Managed Device instrumented tasks (`apiXXDebugAndroidTest`) fail during setup: GMD's emulator **snapshot creation times out** (`AvdSnapshotHandler$EmulatorSnapshotCannotCreatedException`, retries 5x, each reboot = the 'cycling' we chased for hours). The emulator itself boots fine (verified: 8GB RAM, `boot_completed=1`, shell-responsive) — only GMD's snapshot step is broken. Root cause: AEHD 2.2 can't complete the snapshot save/load (also caused the earlier `-check-snapshot-loadable` hangs).
## Scope
All LOCAL GMD instrumented tasks: coverage **lane 3 (#248)**, **lane 5 (#250)**, AND the **/preflight api35/api36 steps** (GMD tasks added in #266) — so preflight as designed fails locally on this box. GMD-specific: **CI is unaffected** (it uses `reactivecircus/android-emulator-runner` + `connectedDebugAndroidTest`, no GMD).
## Fix
Use `connectedDebugAndroidTest` against a manually-provisioned emulator (cold boot, `-no-snapshot`) for local instrumented tests — same technique as `.claude/skills/preflight/api37_e2e.py` and CI. Generalize that api37 script to any API level and switch the preflight api35/api36 steps (and local coverage-lane validation) to it. (Optionally investigate disabling GMD snapshots / bumping setupTimeout, but connectedDebugAndroidTest is the known-reliable path.)
## DoD
Preflight runs api35/36/37 locally via connectedDebugAndroidTest (no GMD), green on this machine; the AEHD/GMD-snapshot limitation documented.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Finding
On this machine (Windows + AEHD hypervisor), Gradle Managed Device instrumented tasks (
apiXXDebugAndroidTest) fail during setup: GMD's emulator snapshot creation times out (AvdSnapshotHandler$EmulatorSnapshotCannotCreatedException, retries 5x, each reboot = the 'cycling' we chased for hours). The emulator itself boots fine (verified: 8GB RAM,boot_completed=1, shell-responsive) — only GMD's snapshot step is broken. Root cause: AEHD 2.2 can't complete the snapshot save/load (also caused the earlier-check-snapshot-loadablehangs).Scope
All LOCAL GMD instrumented tasks: coverage lane 3 (#248), lane 5 (#250), AND the /preflight api35/api36 steps (GMD tasks added in #266) — so preflight as designed fails locally on this box. GMD-specific: CI is unaffected (it uses
reactivecircus/android-emulator-runner+connectedDebugAndroidTest, no GMD).Fix
Use
connectedDebugAndroidTestagainst a manually-provisioned emulator (cold boot,-no-snapshot) for local instrumented tests — same technique as.claude/skills/preflight/api37_e2e.pyand CI. Generalize that api37 script to any API level and switch the preflight api35/api36 steps (and local coverage-lane validation) to it. (Optionally investigate disabling GMD snapshots / bumping setupTimeout, but connectedDebugAndroidTest is the known-reliable path.)DoD
Preflight runs api35/36/37 locally via connectedDebugAndroidTest (no GMD), green on this machine; the AEHD/GMD-snapshot limitation documented.