Android SDK API 29 constant timeout after successful run (also sometimes 26 and 28)

[TWiStErRob]

Hi, after running the Android emulator on Ubuntu with kvm, I'm getting this behavior consistently (2 different projects, both trigger on 29 ONLY):

Terminate Emulator
  /usr/local/lib/android/sdk/platform-tools/adb -s emulator-5554 emu kill
  OK: killing emulator, bye bye
  OK
INFO    | Wait for emulator (pid 2398) 20 seconds to shutdown gracefully before kill;you can set environment variable ANDROID_EMULATOR_WAIT_TIME_BEFORE_KILL(in seconds) to change the default value (20 seconds)
INFO    | Discarding the changed state: command-line flag
WARNING | Discarding the changed state (command-line flag).
ERROR   | stop: Not implemented
Error: The action has timed out.

https://github.com/TWiStErRob/net.twisterrob.colorfilters/actions/runs/7675870108/job/20922671781?pr=284#step:11:1478

also at https://github.com/TWiStErRob/net.twisterrob.inventory/actions/runs/7677783691 (see first 3 attempts)

I'm raising here in case you know what could be wrong, or where this would come from.

[TWiStErRob]

Ah, you have the same issue on this repo:
https://github.com/ReactiveCircus/android-emulator-runner/actions/workflows/main.yml

[TWiStErRob]

Huh, the output is exactly the same for all API levels, checked 23 and 33, except they don't hang.

[TWiStErRob]

Few example runs with many API levels (trivial workflow, 1 ui test):
https://github.com/TWiStErRob/net.twisterrob.inventory/actions/runs/7717962548
https://github.com/TWiStErRob/net.twisterrob.inventory/actions/runs/7717761833
https://github.com/TWiStErRob/net.twisterrob.inventory/actions/runs/7716629066
(note: I removed 29, because it was always timing out)

[johnjohndoe]

➕ Same here: https://github.com/EventFahrplan/EventFahrplan/actions
Interestingly, API 29 ran when I added it a few days ago: https://github.com/EventFahrplan/EventFahrplan/actions/runs/7776856384

[grodin]

Also related: #381, #385

[vitorhugods]

Hi, after running the Android emulator on Ubuntu with kvm

Also facing this after enabling KVM. It's ridiculously faster, but now it fails on shutdown after 20s timeout :(

Seems to be specific to KVM?

[vaind]

duplicate of #385 (which is newer but has more activity and is more generic)