Status Update
Comments
sp...@google.com <sp...@google.com>
sp...@google.com <sp...@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?
an...@google.com <an...@google.com> #4
No idea why the scan does not contain log information, here you are:
ga...@gmail.com <ga...@gmail.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?
ga...@gmail.com <ga...@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.
Description
Adding
.with(BooleanOption.ENABLE_PROFILE_JSON, true)
to a test inConfigurationPerSourceSetTest
causes the test to fail with the following error message: