CI: 4.4 says it's ready before it actually is

Its boot animation is "stopped" but on my laptop the CPU is still at 100%,
which means it's probably still working and not ready yet. The tests fail if
you run them right after wait-for-emulator is done. If you wait a few seconds
though, they do work since the CPU load drops.

Until we can figure out a better solution, have a generous 30-second sleep
after it tells us it's ready.
This commit is contained in:
Daniel Martí 2015-09-09 21:47:15 -07:00
parent e3400006a9
commit 3fe1893336

View File

@ -44,6 +44,7 @@ test:
- emulator -force-32bit -avd fcl-test -no-skin -no-audio -no-window & - emulator -force-32bit -avd fcl-test -no-skin -no-audio -no-window &
- ./F-Droid/tools/wait-for-emulator - ./F-Droid/tools/wait-for-emulator
- adb shell input keyevent 82 - adb shell input keyevent 82
- sleep 30 # 4.4 says it's ready before it actually is
- echo " == Running Android tests on the 4.4.4 emulator" - echo " == Running Android tests on the 4.4.4 emulator"
- ADB_INSTALL_TIMEOUT=8 gradle connectedCheck - ADB_INSTALL_TIMEOUT=8 gradle connectedCheck
- echo " == Stopping Android 4.4.4 emulator" - echo " == Stopping Android 4.4.4 emulator"