[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Title: Message Title Andy Piper reopened an issue Does not work on current android releases. Android Debug Bridge version 1.0.32 Revision 57224c5cff69-android Jenkins / JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Change By: Andy Piper Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Title: Message Title Andy Piper commented on JENKINS-11952 Re: Emulator occasionally hangs indefinitely on startup, unable to connect adb This does not work. andypiper:platform-tools andy$ ./adb -s localhost:5554 shell getprop init.svc.bootanim error: device 'localhost:5554' not found Maybe something changed in the latest releases of android, but this mechanism is now invalid as a means of connecting to the emulator Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Christopher Orr resolved JENKINS-11952 as Fixed Emulator occasionally hangs indefinitely on startup, unable to connect adb Version 2.13 of the plugin has been released, which includes the updates discussed here. Change By: Christopher Orr (12/Mar/15 9:11 AM) Status: Reopened Resolved Assignee: RichardMortimer ChristopherOrr Resolution: Fixed 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Christopher Orr closed JENKINS-11952 as Fixed Emulator occasionally hangs indefinitely on startup, unable to connect adb I'm marking this issue as closed, though I'm aware of the likelihood that not everything is working brilliantly on every machine, all the time. But if there are still obvious issues in 2.13, let's please open a clean issue. Change By: Christopher Orr (12/Mar/15 9:13 AM) Status: Resolved Closed 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Joe Hansche commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I tend to agree with Christopher Orr. Out of the last ~7 builds that were attempted, these were the results: -ports 5743,5744 Worked -ports 5849,5850 Failed to start -ports 5705,5706 Failed to start -ports 5886,5887 Worked -ports 5719,5720 Worked -ports 5619,5620 Failed to start -ports 5866,5867 Worked -ports 5822,5823 Worked So this means it does not seem to be affected by the even/odd pairs. 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Christopher Orr commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Erik Ingman: I tried this change a month or so ago after somebody mentioned that documentation to me, but I found that it made no difference. From re-reading the Android source code, I couldn't see any obvious technical reason why the ports have to be in that form (and only the "-port" flag, not "-ports" enforces it anyway), the "maximum" port number hasn't been 5584 for a long time, adb does recognise emulators started on high ports, and I also looked through lots of build logs for evidence that the user port being even and in that range makes a difference — I didn't find anything conclusive (in fact, emulator startup was more likely to fail in that case). In addition, the code in this pull request doesn't guarantee that the first port will be even, so I'll have to be skeptical about your claims But if it turns out that this change nevertheless helps, then that's good to know. So what are the results you are seeing? Which OS are the emulator builds running on, and what is the emulator config? How many builds were failing previously, compared to now, and is that with builds whose user port is actually even? 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Erik Ingman commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb We have solved this on our end, it seems to work every time. According to the Android Emulator docs "The console port number must be an even integer between 5554 and 5584, inclusive. port+1 must also be free and will be reserved for ADB." So we've created a PR, see https://github.com/jenkinsci/android-emulator-plugin/pull/48 /Erik @ www.blocket.se 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
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
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
akosmaroy commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I have similar issues as reported by others: $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb -s emulator-5847 shell getprop dev.bootcomplete error: device offline installing the current snapshot HPI file manually seems to have solved the problem 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
SCM/JIRA link daemon commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Code changed in jenkins User: Christopher Orr Path: src/main/java/hudson/plugins/android_emulator/AndroidEmulatorContext.java http://jenkins-ci.org/commit/android-emulator-plugin/7949052acba9181ede1ecfed630b0059f113e9de Log: JENKINS-11952 Return to the "localhost:" style of connecting to emulators. For some reason, connecting to the emulator in this manner appears to be somwehat more reliable than connecting with the regular "emulator-" style. From the various JIRA issues opened against the most recent plugin releases, this instability seems to affect Mac OS X more than other operating systems. Now we use "localhost:", while sticking to a four-digit port number, as some tools seem to assume that the emulator port is always four-digits. While it's still a problem that ddmlib — as used by tools like the Maven Android plugin — only recognise emulators with the "emulator-" scheme, this should not be a problem, as the emulator itself at startup registers with adb in this style. While this means that running "adb devices" may show two connected devices (e.g. "emulator-5554" and "localhost:"), libraries like ddmlib will use the "emulator" variant, while build steps that call `adb` will automatically read the ANDROID_SERIAL environment vairable and use the "localhost" variant. 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
SCM/JIRA link daemon commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Code changed in jenkins User: Christopher Orr Path: src/main/java/hudson/plugins/android_emulator/AndroidEmulator.java http://jenkins-ci.org/commit/android-emulator-plugin/5bdae99c654d40416a37af1bd3cca30f9db11543 Log: Revert "JENKINS-11952 Remove redundant (dis)connect calls while waiting for startup." This reverts commit f2fcd2f7d9c12cfd9b8de7cb3ae18049ef056db7. This is required as, per the previous commit, we're using the "localhost" style of emulator connection string once again. Compare: https://github.com/jenkinsci/android-emulator-plugin/compare/bd2fbec33e6f...5bdae99c654d 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Christopher Orr commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb So.. I switched back to the seemingly more reliable "localhost-" way of connecting to emulators, while also making sure we stick to four-digit port numbers for compatibility with (older) tools that depend on that. While I've often found these problems hard to reproduce, I've been doing lots of testing on a MacBook Pro, as Mac OS X seemed to be the OS worst affected by various "device offline" issues. The current code seems to work fairly reliably on OS X (and on Linux), and I've made a bunch of other improvements to the plugin recently. Everything tends to work pretty smoothly in my large test Jenkins jobs, where I set up a matrix of about ten different Android OS versions and get them to start up, and run an adb command. However, I still very often see unexplained failures on OS X when making the job do something useful, like installing an APK. I've tried running the jobs in serial, and disabling the background logcat thread (i.e. to minimise any disruptions to the emulator and adb), yet APK installation will either time out, or the adb connection will vanish. Anyway, it would be great if as many people as possible could test the latest build of the plugin. Download the ".hpi" file from the following link, then you can upload it to your Jenkins instance via the Plugin Manager Advanced Upload; you will then need to restart Jenkins: https://jenkins.ci.cloudbees.com/job/plugins/job/android-emulator-plugin/lastStableBuild/org.jenkins-ci.plugins$android-emulator/ I would like to do a plugin release within the next week or so, though the Jenkins infrastructure for releasing is currently down (INFRA-240). All the more reason to get testing. Thanks, everyone. 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
P Oh commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb forgot to add, plugin version: 2.13-SNAPSHOT (private-5bdae99c-jenkins) 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
P Oh
commented on JENKINS-11952
Emulator occasionally hangs indefinitely on startup, unable to connect adb
Master server:
ubuntu 14.04
jenkins version 1.596
slave:
ubuntu 14.04
java version "1.7.0_72"
Java(TM) SE Runtime Environment (build 1.7.0_72-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.72-b04, mixed mode)
android sdk tools 24.0.2
android platform tools 21
android sdk build-tools 21.1.2
It seems to connect at some point but does not validate the connection correctly. Heres my semi-sanitized build log. Let me know where I can locate any other logs which may be of help.
Started by upstream project "ad-pipeline" build number 36
originally caused by:
Started by an SCM change
EnvInject - Loading node environment variables.
Building remotely on android-slave (android) in workspace *
Cloning the remote Git repository
Cloning repository *
/usr/bin/git init * # timeout=10
Fetching upstream changes from *
/usr/bin/git --version # timeout=10
using GIT_SSH to set credentials *
/usr/bin/git -c core.askpass=true fetch --tags --progress * +refs/heads/:refs/remotes/origin/
/usr/bin/git config remote.origin.url * # timeout=10
/usr/bin/git config remote.origin.fetch +refs/heads/:refs/remotes/origin/ # timeout=10
/usr/bin/git config remote.origin.url * # timeout=10
Fetching upstream changes from *
using GIT_SSH to set credentials *
/usr/bin/git -c core.askpass=true fetch --tags --progress * +refs/heads/:refs/remotes/origin/
/usr/bin/git rev-parse refs/remotes/origin/develop^{commit} # timeout=10
/usr/bin/git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10
Checking out Revision * (refs/remotes/origin/develop)
/usr/bin/git config core.sparsecheckout # timeout=10
/usr/bin/git checkout -f *
/usr/bin/git rev-list * # timeout=10
Allocating TCP port AD_PIPELINE_INSTRUMENTATION_PORT
- Assigned 48374
TCP port allocation complete
$ /opt/android-sdk-linux/tools/android list target
android Using Android SDK: /opt/android-sdk-linux
android Creating Android AVD: */ad-pipeline-instrumentation/19/.android/avd/hudson_en-US_320_1080x1920_Google_Inc._Google_APIs_18_armeabi-v7a_jenkins.avd
android /opt/android-sdk-linux/tools/android create avd -f -a -c 200M -s 1080x1920 -n hudson_en-US_320_1080x1920_Google_Inc._Google_APIs_18_armeabi-v7a_jenkins -t "Google Inc.:Google APIs:18" --abi armeabi-v7a
android Waiting 10 seconds before starting emulator...
$ /opt/android-sdk-linux/platform-tools/adb start-server
daemon not running. starting it now on port 7700 *
daemon started successfully *
$ /opt/android-sdk-linux/platform-tools/adb start-server
android Starting Android emulator
$ /opt/android-sdk-linux/tools/emulator64-arm -no-boot-anim -ports 7698,7699 -prop persist.sys.language=en -prop persist.sys.country=US -avd hudson_en-US_320_1080x1920_Google_Inc._Google_APIs_18_armeabi-v7a_jenkins -no-snapshot-load -no-snapshot-save -no-window -no-audio -gpu off
$ /opt/android-sdk-linux/platform-tools/adb connect localhost:7699
connected to localhost:7699
android Waiting for emulator to finish booting...
$ /opt/android-sdk-linux/platform-tools/adb -s localhost:7699 shell getprop init.svc.bootanim
error: device offline
$ /opt/android-sdk-linux/platform-tools/adb connect localhost:7699
$ /opt/android-sdk-linux/platform-tools/adb -s localhost:7699 shell getprop init.svc.bootanim
error: device offline
$ /opt/android-sdk-linux/platform-tools/adb connect localhost:7699
$ /opt/android-sdk-linux/platform-tools/adb -s localhost:7699 shell getprop init.svc.bootanim
error: device offline
$ /opt/android-sdk-linux/platform-tools/adb disconnect localhost:7699
$ /opt/android-sdk-linux/platform-tools/adb connect localhost:7699
$ /opt/android-sdk-linux/platform-tools/adb -s localhost:7699 shell getprop init.svc.bootanim
$ /opt/android-sdk-linux/platform-tools/adb connect localhost:7699
$ /opt/android-sdk-linux/platform-tools/adb -s localhost:7699 shell getprop init.svc.bootanim
$ /opt/android-sdk-linux/platform-tools/adb connect localhost:7699
$ /opt/android-sdk-linux/platform-tools/adb -s localhost:7699 shell getprop init.svc.bootanim
$ /opt/android-sdk-linux/platform-tools/adb disconnect localhost:7699
$ /opt/android-sdk-linux/platform-tools/adb connect localhost:7699
$ /opt/android-sdk-linux/platform-tools/adb -s localhost:7699 shell getprop init.svc.bootanim
$ /opt/android-sdk-linux/platform-tools/adb connect localhost:7699
$
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Juan Sotuyo commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I too see this with snapshots enabled (and existing, wiping the existing snapshot also works). Once I disabled snapshots it started working again. 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Thierry-Dimitri Roy commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I was able to further analyze the problem. I saw the emulator running on port 5763 with the deamon running on the port 5764. But when I ran the command: adb -P 5764 devices It didn't list any devices. Then I tried connecting directly to the emulator with the command: adb -P 5764 connect localhost:5763 It successfully connected! Then the 'devices' command showed the emulator. And running adb -P 5764 shell getprop init.svc.bootanim return the 'stopped' result. I have modified the jenkins plugin and I no longer see the timeout problem. I have created a pull request. Hope this help other people! 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Tobias Schumacher commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Hi. Here's my configuration. Computer: Mac OS X 10.9.5 Emulator: API Level: android-18 screen density: 160 screen resolution: HVGA targetabi: armeabi-v7a emulator options: emulator executable: Delete emulator after build: checked Startup delay: 20 seconds Android SDK Manager Revision: 23.0.5 Android API 18: SDK Platform Revision 3 Google API Revision 3 Jenkins: Version: 1.569 Android Emulator Plugin Version: 2.12 (official version from jenkins plugin management) 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Christopher Orr commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Thanks for the detailed info, Tobias (though your logs show x86, but your config ARMv7a?). I'll try these configs for myself, and I'll give it a go on a Mac. 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Tobias Schumacher commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I can only find two files with the name x86 included at the project. At the build log at line 11 I create the emulator with "--abi armeabi-v7a". Maybe you looked at the log of Thierry-Dimitri Roy or did you look at this log? 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Christopher Orr commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Oops, sorry, you're right! In that case, thanks Thierry for the detailed logs, and thank you for your detailed logs in the past and the info now How consistently do you see the failure-to-start problem? 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Tobias Schumacher commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb No problem. The problem occurs very different. From 10.12.14 (dd.mm.yy) until today I saw this problem 9 times at 48 builds. Sometimes the problem occurs 1 time in 2 weeks (14 builds) and then 6 times in 2 weeks (21 builds) (the build will be repeated automatically after the failure-to-start problem. these builds are included at tht build counter). 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Thierry-Dimitri Roy edited a comment on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I can reproduce the problem rather easily. We run our tests continuously and we get connection error one fifth of the time. OS the Jenkins build is running on: Mac OS X 10.8.5 Logs: 02:27:47 android Using Android SDK: /android/sdk/ 02:27:47 android Creating Android AVD: /Users/jenkins/workspace/replica_dev_stable/.android/avd/hudson_fr-CA_160_WXGA800_android-17_x86.avd 02:27:47 android /android/sdk//tools/android create avd -f -a -c 1024M -s WXGA800 -n hudson_fr-CA_160_WXGA800_android-17_x86 -t android-17 --abi x86 02:28:06 android Setting hardware properties: 02:28:06 hw.gpu.enabled: yes 02:28:06 hw.ramSize: 1907M 02:28:06 vm.heapSize: 128 02:28:06 hw.lcd.density: 160 02:28:06 hw.dPad: yes 02:28:06 hw.mainKeys: yes 02:28:06 skin.dynamic: no 02:28:06 skin.name: 1280x800 02:28:06 skin.path: 1280x800 02:28:06 $ /android/sdk//platform-tools/adb start-server 02:28:09 * daemon not running. starting it now on port 5632 * 02:28:09 * daemon started successfully * 02:28:09 $ /android/sdk//platform-tools/adb start-server 02:28:09 android Starting Android emulator 02:28:09 $ /android/sdk//tools/emulator64-x86 -no-boot-anim -ports 5630,5631 -prop persist.sys.language=fr -prop persist.sys.country=CA -avd hudson_fr-CA_160_WXGA800_android-17_x86 -no-snapshot-load -no-snapshot-save -wipe-data 02:28:14 HAX is working and emulator runs in fast virt mode 02:28:15 emulator: emulator window was out of view and was recentered ... 02:39:23 $ /android/sdk//platform-tools/adb -s emulator-5630 shell getprop dev.bootcomplete 02:39:23 error: device not found 02:39:37 $ /android/sdk//platform-tools/adb -s emulator-5630 shell getprop dev.bootcomplete 02:39:37 error: device not found 02:39:50 $ /android/sdk//platform-tools/adb -s emulator-5630 shell getprop dev.bootcomplete 02:39:50 error: device not found 02:40:04 $ /android/sdk//platform-tools/adb -s emulator-5630 shell getprop dev.bootcomplete 02:40:04 error: device not found 02:40:18 android Timed-out after waiting 720 seconds for emulator 02:40:18 android Stopping Android emulator 02:40:18 $ /android/sdk//platform-tools/adb kill-server Any suggestion? I'm more than willing to help you. ... UPDATE Here's a log with a connection that worked: 06:11:12 $ /android/sdk//tools/android list target 06:11:24 android Using Android SDK: /android/sdk/ 06:11:24 android Creating Android AVD: /Users/jenkins/workspace/replica_dev_stable/.android/avd/hudson_fr-CA_160_WXGA800_android-17_x86.avd 06:11:24 android /android/sdk//tools/android create avd -f -a -c 1024M -s WXGA800 -n hudson_fr-CA_160_WXGA800_android-17_x86 -t android-17 --abi x86 06:11:44 android Setting hardware properties: 06:11:44 hw.gpu.enabled: yes 06:11:44 hw.ramSize: 1907M 06:11:44 vm.heapSize: 128 06:11:44 hw.lcd.density: 160 06:11:44 hw.dPad: yes 06:11:44 hw.mainKeys: yes 06:11:44 skin.dynamic: no 06:11:44 skin.name: 1280x800 06:11:44 skin.path: 1280x800 06:11:44 $ /android/sdk//platform-tools/adb start-server 06:11:47 * daemon not running. starting it now on port 5749 * 06:11:47 * daemon started successfully * 06:11:47 $ /android/sdk//platform-tools/adb start-server 06:11:47 android Starting Android emulator 06:11:47 $ /android/sdk//tools/emulator64-x86 -no-boot-anim -ports 5747,5748 -prop persist.sys.language=fr -prop persist.sys.country=CA -avd hudson_fr-CA_160_WXGA800_android-17_x86 -no-snapshot-load -no-snapshot-save -wipe-data 06:11:53 HAX is working and emulator runs in fast virt mode 06:11:54 emulator: emulator window was out of view and was recentered 06:11:54 06:11:55 $ /android/sdk//platform-tools/adb connect emulator-5747 06:11:55 android Waiting for emulator to finish booting... 06:11:55 $ /android/sdk//platform-tools/adb -s emulator-5747 shell getprop dev.bootcomplete 06:11:55 error: device offline 06:12:09 $ /android/sdk//platform-tools/adb -s emulator-5747 shell getprop dev.bootcomplete 06:12:09 error: device offline 06:12:22 $ /android/sdk//platform-tools/adb -s emulator-5747 shell getprop dev.bootcomplete 06:12:22 $ /android/sdk//platform-tools/adb -s emulator-5747 logcat -v time 06:12:22 android Emulator is ready for use (took 35 seconds) This message is automatically generated by JIRA.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Christopher Orr commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I was just prompted to look at the connection code again and noticed that — contrary to what I wrote in my commit just above — we're not actually using the same port range that the emulator listens on and that adb checks for emulator-* instances. From double-checking the qemu and adb source, the port range should be 5554 to 5681 (the number of concurrent emulators was increased (though not 100% consistently throughout the code) from 16 to 64 a while ago). I wonder whether using this port range would help fix the adb amnesia problem where it somehow forgets devices (i.e. changes from "device offline" to "device not found". Perhaps if we use the "blessed" port range, adb will automatically re-connnect? 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Christopher Orr commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Though as ever, I can only rarely reproduce these issues, which makes testing ever-so-slightly difficult. Maybe I need to try it on a Mac or Windows? For anybody who has this issue, it would be nice to know what config is being used: OS the Jenkins build is running on Emulator config: API level screen resolution target ABI emulator options emulator executable 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Thierry-Dimitri Roy commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I can reproduce the problem rather easily. We run our tests continuously and we get connection error one fifth of the time. OS the Jenkins build is running on: Mac OS X 10.8.5 Logs: 02:27:47 android Using Android SDK: /android/sdk/ 02:27:47 android Creating Android AVD: /Users/jenkins/workspace/replica_dev_stable/.android/avd/hudson_fr-CA_160_WXGA800_android-17_x86.avd 02:27:47 android /android/sdk//tools/android create avd -f -a -c 1024M -s WXGA800 -n hudson_fr-CA_160_WXGA800_android-17_x86 -t android-17 --abi x86 02:28:06 android Setting hardware properties: 02:28:06 hw.gpu.enabled: yes 02:28:06 hw.ramSize: 1907M 02:28:06 vm.heapSize: 128 02:28:06 hw.lcd.density: 160 02:28:06 hw.dPad: yes 02:28:06 hw.mainKeys: yes 02:28:06 skin.dynamic: no 02:28:06 skin.name: 1280x800 02:28:06 skin.path: 1280x800 02:28:06 $ /android/sdk//platform-tools/adb start-server 02:28:09 * daemon not running. starting it now on port 5632 * 02:28:09 * daemon started successfully * 02:28:09 $ /android/sdk//platform-tools/adb start-server 02:28:09 android Starting Android emulator 02:28:09 $ /android/sdk//tools/emulator64-x86 -no-boot-anim -ports 5630,5631 -prop persist.sys.language=fr -prop persist.sys.country=CA -avd hudson_fr-CA_160_WXGA800_android-17_x86 -no-snapshot-load -no-snapshot-save -wipe-data 02:28:14 HAX is working and emulator runs in fast virt mode 02:28:15 emulator: emulator window was out of view and was recentered ... 02:39:23 $ /android/sdk//platform-tools/adb -s emulator-5630 shell getprop dev.bootcomplete 02:39:23 error: device not found 02:39:37 $ /android/sdk//platform-tools/adb -s emulator-5630 shell getprop dev.bootcomplete 02:39:37 error: device not found 02:39:50 $ /android/sdk//platform-tools/adb -s emulator-5630 shell getprop dev.bootcomplete 02:39:50 error: device not found 02:40:04 $ /android/sdk//platform-tools/adb -s emulator-5630 shell getprop dev.bootcomplete 02:40:04 error: device not found 02:40:18 android Timed-out after waiting 720 seconds for emulator 02:40:18 android Stopping Android emulator 02:40:18 $ /android/sdk//platform-tools/adb kill-server Any suggestion? I'm more than willing to help you. ... 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Tobias Schumacher commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Taiki Sugawara: I'm using the text-finder and the naginator plugin. At the text-finder plugin, I search at the console output for the _expression_ "Timed-out after waiting 720 seconds for emulator" (leave "Files" empty). If this _expression_ was found then the build will be unstable (check the unstable if found checkbox). At the naginator plugin I checked the "Rerun build for unstable builds as well as failures" checkbox and I try again to run the job after 500 seconds (shorter is possible too). I configuered also that the build will be repeated 5 times. I hope this will help you with your problem. @Richard Mortimer: Maybe you can add this workaround to your documentation. 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Tobias Schumacher edited a comment on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Taiki Sugawara: I'm using the text-finder and the naginator plugin. At the text-finder plugin, I search at the console output for the _expression_ "Timed-out after waiting 720 seconds for emulator" (leave "Files" empty). If this _expression_ was found then the build will be unstable (check the unstable if found checkbox). At the naginator plugin I checked the "Rerun build for unstable builds as well as failures" checkbox and I try again to run the job after 500 seconds (shorter is possible too). I configuered also that the build will be repeated 5 times. I hope this will help you with your problem. EDIT: At the naginator plugin you need to open the extended options and check "only rerun build if regular _expression_ is found in output" and paste the time-out message into the "regular _expression_ to search for" field. Without this the build will be repeated even the build is failing because of a source code error. @Richard Mortimer: Maybe you can add this workaround to your documentation. 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Tobias Schumacher edited a comment on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Hi. I still have this issue. Sometimes the emulator starts correctly. Can you add an option to choose, that the build will fail, if the emulator doesn't start (like a checkbox)? I would like to have this feature for the issues "error: device offline" and "error: device not found". I tried to repeat the build with naginator plugin but this is only working with a failed build job (or unstable). Or do you know any other way to repeat the build job? Thanks EDIT: I found the Text-finder plugin. I will work with it to change the job result to unstable. Then I can repeat the build with the naginator plugin. 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Taiki Sugawara commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I still have this issue too. Would you add adb connect timeout for workaround of this issue? 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.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Tobias Schumacher commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Hi. I still have this issue. Sometimes the emulator starts correctly. Can you add an option to choose, that the build will fail, if the emulator doesn't start (like a checkbox)? I would like to have this feature for the issues "error: device offline" and "error: device not found". I tried to repeat the build with naginator plugin but this is only working with a failed build job (or unstable). Or do you know any other way to repeat the build job? Thanks 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.
