search

ReactiveCircus / android-emulator-runner

A GitHub Action for installing, configuring and running hardware-accelerated Android Emulators on macOS virtual machines.
Apache License 2.0
977 stars 193 forks source link

adb cannot connect on ubuntu-latest today #390

Closed finagolfin closed 6 months ago

finagolfin commented 7 months ago

I have been using this action on macos-latest, for hardware acceleration, but now that github switched that to macOS 14 arm64 and I noticed that there is now hw accel on linux too, I switched back to running the emulator on linux.

That worked fine in my testing yesterday in a pull, but now that I merged the change and had my CI schedule a test run, adb cannot connect to the emulator anymore. That has consistently failed a dozen times now, so it's not just some flakiness.

I'm setting the KVM change in both runs, so I don't think that's it, and I don't see any runner image changes since yesterday either.

Anyone else seeing this or know what I'm doing wrong?

finagolfin commented 6 months ago

Somebody else took a look at my CI runs and noticed this error in the failing ones:

ERROR   | Not enough space to create userdata partition. Available: 6570.734375 MB at /home/runner/.android/avd/../avd/test.avd, need 7372.800000 MB.

Turns out the switch to running the emulator on linux worked initially because I was using some cached SDKs when testing the pull, but once my normal CI runs picked up again, they build the SDKs from scratch, using a lot more disk space and getting the emulator launch to fail for lack of space.

I remedied this by deleting my temporary SDK build directory after a new SDK is built, freeing up GBs of space and this emulator action then works fine again.

poponuts commented 2 months ago

hi @finagolfin I know this is closed but can you share the CI steps on deleting my temporary SDK build directory after a new SDK is built. Also, is this step after build?

finagolfin commented 2 months ago

It could be anything in the CI runner that you don't need at that point, really just depends on what you're doing. Yes, after the build, but just before starting the emulator.

I put in these two lines to delete large build and source directories and a downloaded Swift toolchain that was no longer needed. Another project I'm involved with removes a bunch of installed Ubuntu packages and system directories when extra build space is needed, even without running this emulator.

You'll need to remove something like that, whatever you don't need in the CI runner, before running the emulator to avoid this error.