[JIRA] [android-emulator] (JENKINS-24817) Android emulator timeout during launch for 4.4 emulators
Christopher Orr commented on JENKINS-24817 Android emulator timeout during launch for 4.4 emulators Without any console log files, it's hard to tell what the problem is. But I assume this is a duplicate of JENKINS-11952? 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] (JENKINS-24817) Android emulator timeout during launch for 4.4 emulators
JY Hsu commented on JENKINS-24817 Android emulator timeout during launch for 4.4 emulators That doesn't seems to be the same problem, because I am not using snapshot. The console log: $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/tools/android list target android Using Android SDK: /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk android Waiting 30 seconds before starting emulator... $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb start-server android Starting Android emulator $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/tools/emulator -no-boot-anim -ports 46998,43229 -avd Acceptance_LatestOS -no-snapshot-load -no-snapshot-save -qemu -m 512 -enable-kvm emulator: emulator window was out of view and was recentered daemon not running. starting it now on port 45736 * daemon started successfully * $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb connect localhost:43229 android Waiting for emulator to finish booting... $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb -s localhost:43229 shell getprop dev.bootcomplete error: device offline error: device offline $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb connect localhost:43229 $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb -s localhost:43229 shell getprop dev.bootcomplete error: device offline error: device offline $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb connect localhost:43229 $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb -s localhost:43229 shell getprop dev.bootcomplete error: device offline error: device offline $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb disconnect localhost:43229 $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb connect localhost:43229 $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb -s localhost:43229 shell getprop dev.bootcomplete error: device offline error: device offline $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb connect localhost:43229 $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb -s localhost:43229 shell getprop dev.bootcomplete error: device offline error: device offline $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb connect localhost:43229 $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb -s localhost:43229 shell getprop dev.bootcomplete error: device offline error: device offline $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb disconnect localhost:43229 $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb connect localhost:43229 $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb -s localhost:43229 shell getprop dev.bootcomplete error: device offline error: device offline $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb connect localhost:43229 $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb -s localhost:43229 shell getprop dev.bootcomplete error: device offline error: device offline $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb connect localhost:43229 $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb -s localhost:43229 shell getprop dev.bootcomplete error: device offline error: device offline $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb disconnect localhost:43229 $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb connect localhost:43229 $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb -s localhost:43229 shell getprop dev.bootcomplete error: device offline error: device offline $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb connect localhost:43229 $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb -s localhost:43229 shell getprop dev.bootcomplete error: device offline error: device offline $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb connect localhost:43229 $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb -s localhost:43229 shell getprop dev.bootcomplete error: device offline error: device offline $ /root/Downloads/adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb disconnect
[JIRA] [android-emulator] (JENKINS-24817) Android emulator timeout during launch for 4.4 emulators
Christopher Orr resolved JENKINS-24817 as Duplicate Android emulator timeout during launch for 4.4 emulators Duplicates JENKINS-11952. Change By: Christopher Orr (23/Sep/14 12:58 PM) Status: Open Resolved Resolution: Duplicate 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] (JENKINS-24817) Android emulator timeout during launch for 4.4 emulators
JY Hsu created JENKINS-24817 Android emulator timeout during launch for 4.4 emulators Issue Type: Bug Assignee: Christopher Orr Components: android-emulator Created: 23/Sep/14 3:48 AM Description: I have two set of nearly identical jobs. One of them runs 4.1.2 emulators and the other one runs 4.4 emulators. I found that the jobs run 4.4 emulators has significantly higher chance of timeout during emulator launch. In fact, the 4.1.2 emulators almost never fail to launch. I've also upgraded to 2.11.1 and things got significantly worse. The launch time was a lot longer, and launch timeout happened a lot more frequently. There is a similar thread in StackOverFlow: http://stackoverflow.com/questions/23699433/android-emulator-jenkins-plugin-not-working Environment: Android emulator plugin 2.10 Project: Jenkins Priority: Major Reporter: JY Hsu 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.
