Status Update
Comments
kd...@google.com <kd...@google.com>
je...@google.com <je...@google.com>
hu...@google.com <hu...@google.com> #2
The attached Build Scan log shows that the emulator process crashed unexpectedly. Could you rerun your task with --info
and -Pandroid.experimental.testOptions.managedDevices.emulator.showKernelLogging=true
to get more information about the emualtor process logs?
ph...@gmail.com <ph...@gmail.com> #4
No idea why the scan does not contain log information, here you are:
hu...@google.com <hu...@google.com> #5
The link in --info
and -Pandroid.experimental.testOptions.managedDevices.emulator.showKernelLogging=true
, the emulator process output its kernel logging to stdout. Do you see any stacktrace or segfault in the log?
ph...@gmail.com <ph...@gmail.com> #6
That's strange, the repo and the build is public... But I attached the logs as file
ph...@gmail.com <ph...@gmail.com> #7
I looked into the logs and it turns out, the runner didn't have enough disk space. I guess the root cause is the Gradle update causing another Gradle major version (and its new transform-4) folder to cache was too much. Anyway, a better error message of the exit code of GMD would be helpful.
hu...@google.com <hu...@google.com> #8
Thanks for uploading the log! Yes, the emulator kernel log says the issue was the insufficient disk space:
2024-04-02T18:31:45.7078429Z ERROR | Not enough space to create userdata partition. Available: 7177.027344 MB at /home/runner/.config/.android/avd/gradle-managed/dev34_aosp_atd_x86_64_Pixel_2.avd, need 7372.800000 MB.
Also, I agreed that GMD should diagnose errors and can provide better messages.
Let me rename this issue's title to improve the error message for disk space error.
da...@google.com <da...@google.com>
da...@google.com <da...@google.com> #9
I've added a fix that will surface all error messages from the emulator in the exception when it closes unexpectedly.
an...@google.com <an...@google.com> #10
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Meerkat | 2024.3.1 Canary 2
- Android Gradle Plugin 8.9.0-alpha02
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
Description
STEPS TO REPRODUCE:
1. Checkout
2. Run the branch on GitHub using Ubuntu-latest
CMD: ./gradlew :kotlinx-uuid-core:allDevicesCheck -Pandroid.testoptions.manageddevices.emulator.gpu=swiftshader_indirect
Build Scan:
LOG:
------------------
IMPORTANT: Please read
all required information.
------------------
Studio Build:
Version of Gradle Plugin: 8.3.1, 8.4.0-beta01, 8.5.0-alpha01
Version of Gradle: 8.7
Version of Java: 17
OS: Ubuntu 22.04