Details
-
User Story
-
Resolution: Fixed
-
P2: Important
-
production
-
None
-
-
2023wk24FOQtforAndroid, 2023wk26FOQtforAndroid, 2023wk30FOQtforAndroid, 2023wk32FOQtforAndroid, 2023wk34FOQtforAndroid, 2023wk36FOQtforAndroid, 2023wk40FOQtforAndroid, 2023wk42FOQtforAndroid, 2023wk48FOQtforAndroid
-
8d199fd70 (dev), abe7c77d6 (dev), f7f7c9f91 (dev), 1c27f95d0 (dev), e0498fc67 (dev), 23b09c1d2 (dev), 387ff3e6c (6.7), 7f532a7fe (6.7)
Description
The current Android emulator keeps having issues from time to time. The common issue is the failure to launch the emulator properly each time on test VMs. We could try to fix this. We have two options that we could try out:
- Make a snapshot of the avd during the provisioning and then when starting the test vms we could simply load back the snapshot and not do a full cold boot all over again
- Add these flags to the avd launch comman
-no-window -no-boot-anim
Attachments
Issue Links
- covers
-
QTQAINFRA-4628 Prevent Android Emulator from showing a popup dialog on first start
- Closed
- replaces
-
COIN-1013 Timeout starting intent on Android in CI
- Closed
-
QTBUG-103878 qqmlparser times out on Android
- Closed
- resulted from
-
QTQAINFRA-5606 Android Emulator fails to start randomly on RHEL
- Closed
- resulted in
-
QTQAINFRA-5908 ADB logcat output file is always empty
- Closed
(5 mentioned in)