-
-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Job hangs after unknown crash #342
Comments
Solved. For those of you that are struggling with this as well the issue turned out to be the emulator version. One of the latest releases 32.1.12 has a known issue which has been fixed in the latest emulator release. Make sure you are adding |
@safa007 how did you fix it? I've changed my target to here's my config:
PS: if the AVD is re-created, I get the same exception you listed above ( Thanks! |
@carlospontual Make sure to clear your runner's avd, gradle, and .android cache so that a new run can try to download the most up-to-date emulator version. I would double check that the runner is not using that faulty emulator version by checking the logs. |
I don't think I'm using the faulty version, what do you say?
|
@carlospontual could possibly be a different issue then 🤔 |
@safa007 @carlospontual @hostilefork @rfc2822 So I have created an emulator on the macos agent then when launching it, it crashes See the details: 2024-02-20T10:55:14.2113280Z Available Android Virtual Devices: |
We recently started experiencing this issue where we see a crash at the end of the Terminate emulator step, and after this step the job just hangs infinitely until it's cancelled or times out. The logs aren't really helpful, we just see a
UniversalExceptionRaise: (os/kern) failure (5)
at the very end of the job. It does seem like the AVD creation is successful however.I tried resetting the machine this is happening on, and after 2 successful runs we started seeing the issue again. I've tested on v2.25.0 and v2.28.0 and the result is the same on both versions.
Has anyone experienced this recently?
EDIT: After setting
force-avd-creation
tofalse
we are still getting theUniversalExceptionRaise: (os/kern) failure (5)
error however the job does not hang and it correctly moves on to the next step. So it seems this is only happening when a new AVD is being created. We setforce-avd-creation
totrue
on every test run in order to prevent out of memory issues on the emulator.EDIT2: Still seeing the issue with
force-avd-creation
tofalse
as well.Here's our GHA setup
The text was updated successfully, but these errors were encountered: