-
-
Notifications
You must be signed in to change notification settings - Fork 198
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
Emulator randomly not booting #192
Comments
I'm surprised how people are not losing their hair by how flaky those emulators are 😂 |
They are😄 |
So this can happen out of the blue for no reason? No way to overcome that? |
This has bitten me a few times. It's a transient error, and a more robust system (that still acknowledges transient network errors may happen) would have a configurable number of retries with configurable delay before hard-failing. For instance, this works really well for retrying: https://github.com/nick-fields/retry All access to remote resources should be wrapped in similar logic really Is there any appetite for a PR that would implement these sort of robust-ness workarounds? I wanted to move to this action to simplify my scripts, but I used to have them in place when doing what this action does (but manually) in my workflows, and the flakiness is a pain vs my more-complicated-but-more-robust manual way |
PR Request: Wrap emulator boot logic in a configurable loop, defaults to a certain number. |
I've been seeing a lot of flakiness lately in the emulator booting, across many different API levels.
The common thing between the failures seems to be
Warning: An error occurred while preparing SDK package XXX System Image: archive is not a ZIP archive.
. Looks like thesdkmanager --install
call is failing (network error?)Full log
The text was updated successfully, but these errors were encountered: