-
-
Notifications
You must be signed in to change notification settings - Fork 185
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 failed to boot #324
Comments
Also running into the same since last 3 days. |
+1 Also experiencing this for past 3 days. Seems to fail 70-80% of the time |
Hey friends we are hitting this as well with Store |
Same here. Running on 4-core latest ubuntu and it maybe starts 15% of time. |
Same story, timeout in most cases:
|
API 29 with default config is working, but with API 30 I'm facing the same
|
I´m facing the same problem with that API, was everything fine until 2 day ago, and now that |
I have the same problem bytedance/flutter_ume#107 |
It looks like the main workflow of this repo is also failing with the same problem we are all having :/ Is there any more information on what the problem is and when it will probably be fixed? Thank you in advance :) |
Same here for me. Has anyone made any headway? |
has been happening for almost two months now. Are there any other alternate options that anyone is using with Github actions? |
I ended up firing up a Firebase Test Lab test from my Github Action. It's not as elegant as having everything running neatly in my own runner, but it'll do for now. |
I have the same issues with API 31. I will give it a try with API 33. |
Just noting here that we were seeing the same error when using a self-hosted ARM64 runner (always fails with Our current working action is:
|
Having the same issue here |
Having the same issue on the "BuildJet" runner (buildjet-4vcpu-ubuntu-2204) with the following options:
|
And the same with this:
|
I am seeing a similar issue on API 29 and 33 (haven't tried any other), but in my case
|
Same issue:
My YML:
|
Unfortunately, I'm facing exactly the same issue |
Happened in the Android official example project: Log: |
I noticed that in the Android official example project, someone merged in this change with a git commit mentioning "to fix CI" Another PR was linked in the above PR's description where this relevant conversation was held. After seeing this, I decided to implement the free-disk-space action within my workflow and it seems it may have resolved the emulator failing to boot. This is a recent change for my workflow so hopefully I'll know after enough runs if it's truly fixed or not. |
After adding the free-disk-space step
|
Hello Dear Community, Do we have a fix for this issue? I am still running into the problem with the error message below. Can someone please suggest a fix? Error message: Workflow:
Sample workflow - https://github.com/santhoshshetty/MobileAutomation/actions/runs/9391653932/job/25864291597 Any help or suggestions would be greatly appreciated. Thank you! |
@ychescale9 Thanks a lot, and I look forward to your response. Thank you once again. |
@santhoshshetty I looked at your sample workflow and looks like this is the issue:
You're using
Any reason you can't use |
Hello here, it works with |
When running the emulator on GitHub Actions (macos-latest), we occasionally get an error of
Timeout waiting for emulator to boot
. This is probably around 25-30% of test runs that we get this. I did a dive into the differences between a successful build and this error in terms of logs, but couldn't spot anything obvious.The build logs are as follows:
Our workflow file can be found at: https://github.com/ably/ably-asset-tracking-android/blob/main/.github/workflows/emulate.yml
Thanks! :)
The text was updated successfully, but these errors were encountered: