Status Update
Comments
se...@candybytes.com <se...@candybytes.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?
an...@google.com <an...@google.com>
ap...@google.com <ap...@google.com> #4
No idea why the scan does not contain log information, here you are:
na...@google.com <na...@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?
mi...@gmail.com <mi...@gmail.com> #6
That's strange, the repo and the build is public... But I attached the logs as file
an...@google.com <an...@google.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.
ju...@google.com <ju...@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.
Description
Jetpack Compose component(s) used: androidxCompose = "1.3.0-rc01" androidxComposeCompiler = "1.3.2" androidxComposeMaterial3 = "1.0.0-alpha13" androidxComposeMaterial = "1.2.1"
Android Studio Build: Build #AI-222.4167.29.2221.9133400, built on October 4, 2022
Kotlin version: kotlin = "1.7.20"
Steps to Reproduce or Code Sample to Reproduce:
I struggle with a "Key" problem since I updated from androidx.compose "1.3.0-beta03" to "1.3.0-rc01".
I use LazyPagingItems for a LazyVerticalGrid and i add items like this in the LazyGridScope:
But since the library update, when I filter the content (so the paging items are updated in the flow), it throws an Exception. This exception wasn't thrown in the beta03 library version.
Because paging data is changing and elements become null while loading I can't supply a unique key, the App crashes. Is this a bug in the library or what exactly is the best practice when using LazyPagingItems that can change over time if you'd like to work with keys in the LazyGrid?
Stack trace (if applicable):