[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb

[nicholas.pauf...@clio.com (JIRA)]

Nicholas Paufler commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I'm seeing the same thing, even with the latest snapshot plugin (2.13-SNAPSHOT (private-67377031-jenkins). In my case, I wouldn't say it's occasional - i'd say it's more like 90% of the time the emulator will fail to respond. I have Jenkins slaves running on Debian EC2 instances - not using any emulator snapshots, every run is fresh with a clean workspace, so I haven't been able to figure out the difference as to why sometimes they are starting correctly and more often not. Here's an example of a sanitized log from a successful startup: ------------------------------------ Deleting project workspace... Cloning the remote Git repository Cloning repository g...@github.com:####/####.droid.git > git init /var/lib/jenkins/workspace/####.Droid-branches/instrumentation-test # timeout=10 Fetching upstream changes from g...@github.com:####/####.droid.git > git --version # timeout=10 using GIT_SSH to set credentials > git -c core.askpass=true fetch --tags --progress g...@github.com:####/####.droid.git +refs/heads/:refs/remotes/origin/ > git config remote.origin.url g...@github.com:####/####.droid.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/:refs/remotes/origin/ # timeout=10 > git config remote.origin.url g...@github.com:####/####.droid.git # timeout=10 Fetching upstream changes from g...@github.com:####/####.droid.git using GIT_SSH to set credentials > git -c core.askpass=true fetch --tags --progress g...@github.com:####/####.droid.git +refs/heads/:refs/remotes/origin/ > git rev-parse origin/instrumentation-test^{commit} # timeout=10 Checking out Revision #### (origin/instrumentation-test) > git config core.sparsecheckout # timeout=10 > git checkout -f #### > git rev-list #### # timeout=10 Starting xvnc [instrumentation-test] $ vncserver :63 -localhost -nolisten tcp New 'slave20150223:63 ()' desktop is slave20150223:63 Starting applications specified in /var/lib/jenkins/.vnc/xstartup Log file is /var/lib/jenkins/.vnc/slave20150223:63.log $ /var/lib/jenkins/workspace/android-sdk/tools/android list target [android] Using Android SDK: /var/lib/jenkins/workspace/android-sdk [android] Creating Android AVD: /var/lib/jenkins/workspace/####.Droid-branches/instrumentation-test/.android/avd/hudson_en-US_160_WVGA_android-19_armeabi-v7a_instrumentation.avd [android] /var/lib/jenkins/workspace/android-sdk/tools/android create avd -f -a -s WVGA800 -n hudson_en-US_160_WVGA_android-19_armeabi-v7a_instrumentation -t android-19 --abi armeabi-v7a [android] Setting hardware properties: hw.audioInput: no [android] Waiting 10 seconds before starting emulator... $ /var/lib/jenkins/workspace/android-sdk/platform-tools/adb start-server * daemon not running. starting it now on port 9881 * * daemon started successfully * $ /var/lib/jenkins/workspace/android-sdk/platform-tools/adb start-server [android] Starting Android emulator $ /var/lib/jenkins/workspace/android-sdk/tools/emulator -no-boot-anim -ports 9879,9880 -prop persist.sys.language=en -prop persist.sys.country=US -avd hudson_en-US_160_WVGA_android-19_armeabi-v7a_instrumentation -no-snapshot-load -no-snapshot-save -no-audio -gpu off Failed to create Context 0x3005 emulator: WARNING: Could not initialize OpenglES emulation, using software renderer. emulator: emulator window was out of view and was recentered $ /var/lib/jenkins/workspace/android-sdk/platform-tools/adb connect localhost:9880 connected to localhost:9880 [android] Waiting for emulator to finish booting... $ /var/lib/jenkins/workspace/android-sdk/platform-tools/adb -s localhost:9880 shell getprop init.svc.bootanim error: device offline $ /var/lib/jenkins/workspace/android-sdk/platform-tools/adb connect localhost:9880 $ /var/lib/jenkins/workspace/android-sdk/platform-tools/adb -s localhost:9880 shell getprop init.svc.bootanim $ /var/lib/jenkins/workspace/android-sdk/platform-tools/adb -s localhost:9880 logcat -v time $ /var/lib/jenkins/workspace/android-sdk/platform-tools/adb connect localhost:9880 [android] Emulator is ready for use (took 20 seconds) [Gradle] - Launching build. [instrumentation-test] $ /var/lib/jenkins/tools/hudson.plugins.gradle.GradleInstallation/Gradle_2.2.1_####.Droid_/gradle-2.2.1/bin/gradle --debug --info --stacktrace assemble Starting Build ---------------------------- And here's it failing: ---------------------------- Deleting project workspace... done Cloning the remote Git repository Cloning repository g...@github.com:#### > git init /var/lib/jenkins/workspace/####.Droid-branches/instrumentation-test # timeout=10 Fetching upstream changes from g...@github.com:####/####.droid.git > git --version # timeout=10 using GIT_SSH to set credentials > git -c core.askpass=true fetch --tags --progress g...@github.com:####/####.droid.git +refs/heads/:refs/remotes/origin/ > git config remote.origin.url g...@github.com:####/####.droid.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/:refs/remotes/origin/ # timeout=10 > git config remote.origin.url g...@github.com:####/####.droid.git # timeout=10 Fetching upstream changes from g...@github.com:####/####.droid.git using GIT_SSH to set credentials > git -c core.askpass=true fetch --tags --progress g...@github.com:####/####.droid.git +refs/heads/:refs/remotes/origin/ > git rev-parse origin/instrumentation-test^{commit} # timeout=10 Checking out Revision #### (origin/instrumentation-test) > git config core.sparsecheckout # timeout=10 > git checkout -f #### > git rev-list #### # timeout=10 Starting xvnc [instrumentation-test] $ vncserver :95 -localhost -nolisten tcp New 'slave20150223:95 ()' desktop is slave20150223:95 Starting applications specified in /var/lib/jenkins/.vnc/xstartup Log file is /var/lib/jenkins/.vnc/slave20150223:95.log $ /var/lib/jenkins/workspace/android-sdk/tools/android list target [android] Using Android SDK: /var/lib/jenkins/workspace/android-sdk [android] Creating Android AVD: /var/lib/jenkins/workspace/####.Droid-branches/instrumentation-test/.android/avd/hudson_en-US_160_WVGA_android-19_armeabi-v7a_instrumentation.avd [android] /var/lib/jenkins/workspace/android-sdk/tools/android create avd -f -a -s WVGA800 -n hudson_en-US_160_WVGA_android-19_armeabi-v7a_instrumentation -t android-19 --abi armeabi-v7a [android] Setting hardware properties: hw.audioInput: no [android] Waiting 10 seconds before starting emulator... $ /var/lib/jenkins/workspace/android-sdk/platform-tools/adb start-server daemon not running. starting it now on port 9227 * daemon started successfully * $ /var/lib/jenkins/workspace/android-sdk/platform-tools/adb start-server [android] Starting Android emulator $ /var/lib/jenkins/workspace/android-sdk/tools/emulator -no-boot-anim -ports 9225,9226 -prop persist.sys.language=en -prop persist.sys.country=US -avd hudson_en-US_160_WVGA_android-19_armeabi-v7a_instrumentation -no-snapshot-load -no-snapshot-save -no-audio -gpu off $ /var/lib/jenkins/workspace/android-sdk/platform-tools/adb connect localhost:9226 connected to localhost:9226 [android] Waiting for emulator to finish booting... $ /var/lib/jenkins/workspace/android-sdk/platform-tools/adb -s localhost:9226 shell getprop init.svc.bootanim error: device offline $ /var/lib/jenkins/workspace/android-sdk/platform-tools/adb connect localhost:9226 $ /var/lib/jenkins/workspace/android-sdk/platform-tools/adb -s localhost:9226 shell getprop init.svc.bootanim error: device offline $ /var/lib/jenkins/workspace/android-sdk/platform-tools/adb connect localhost:9226 $ /var/lib/jenkins/workspace/android-sdk/platform-tools/adb -s localhost:9226 shell getprop init.svc.bootanim error: device offline $ /var/lib/jenkins/workspace/android-sdk/platform-tools/adb disconnect localhost:9226 $ /var/lib/jenkins/workspace/android-sdk/platform-tools/adb connect localhost:9226 $ /var/lib/jenkins/workspace/android-sdk/platform-tools/adb -s localhost:9226 shell getprop init.svc.bootanim error: device offline ------------ In the failure case, it will sit there repeatedly cycling through the commands and the error: device offline until it times out and the job aborts.

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.