Fixed
Status Update
Comments
da...@google.com <da...@google.com>
da...@google.com <da...@google.com> #2
I am running into the same problem running Flutter integration tests on an android emulator:
https://travis-ci.org/brianegan/flutter_architecture_samples/builds/517050722
The failing build is using:
Android emulator version 28.0.25.0 (build_id 5395263) (CL:77b96786ddf712e1477c6e05cddb09526043faef)
(https://travis-ci.org/brianegan/flutter_architecture_samples/jobs/517108854#L1102 )
... which fails to start while issuing the error message:
emulator: ERROR: detected a hanging thread 'QEMU1 main loop'. No response for 105001 ms
(https://travis-ci.org/brianegan/flutter_architecture_samples/jobs/517050724#L1284 )
By pinning the emulator as suggested by Pietro to:
Android emulator version 28.0.23.0 (build_id 5264690) (CL:be2be19ca0131957449e8c0ded5e55070f9537b0)
(https://travis-ci.org/brianegan/flutter_architecture_samples/jobs/517108854#L1121 )
... all the emulators start-up successfully and the jobs in the build succeed:
https://travis-ci.org/brianegan/flutter_architecture_samples/builds/517108852
The failing build is using:
Android emulator version 28.0.25.0 (build_id 5395263) (CL:77b96786ddf712e1477c6e05cddb09526043faef)
(
... which fails to start while issuing the error message:
emulator: ERROR: detected a hanging thread 'QEMU1 main loop'. No response for 105001 ms
(
By pinning the emulator as suggested by Pietro to:
Android emulator version 28.0.23.0 (build_id 5264690) (CL:be2be19ca0131957449e8c0ded5e55070f9537b0)
(
... all the emulators start-up successfully and the jobs in the build succeed:
br...@gmail.com <br...@gmail.com> #3
Thank you for your feedback. Team may reach out for more feedback in reproducing or triaging this issue.
Description
When you toggle the
viewBinding [enabled|disabled]
setting in your module's build.gradle, this should propagate to our system and tell it to re-evaluate its cache. Particularly for our code that looks like:we currently don't notify
getViewBindingEnabledModules()
that there's now a new view binding module (or one view binding module less) than before, so we miss out on all the layouts in that module (until the user restarts Studio or modifies their project in a way that resets the cache indirectly).Data binding is already doing something like this -- we just need to copy it.