[JIRA] (JENKINS-37614) [android] Emulator did not appear to start; giving up
Title: Message Title Ganesh Bhat commented on JENKINS-37614 Re: [android] Emulator did not appear to start; giving up Agree with Jun Liu. I'm also facing same problem. Any workaround for this issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-37614) [android] Emulator did not appear to start; giving up
Title: Message Title bala kamath commented on JENKINS-37614 Re: [android] Emulator did not appear to start; giving up Even i am facing same issue: Jenkins 2.38. AndroidEmultorPlugin version: 2.15. when will this change be available? and which version? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37614) [android] Emulator did not appear to start; giving up
Title: Message Title lz1asl commented on JENKINS-37614 Re: [android] Emulator did not appear to start; giving up There is a pull request pending https://github.com/jenkinsci/android-emulator-plugin/pull/63, please have a look. Many thanks to ikolomiyets. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37614) [android] Emulator did not appear to start; giving up
Title: Message Title lz1asl commented on JENKINS-37614 Re: [android] Emulator did not appear to start; giving up According to http://stackoverflow.com/questions/19349222/jenkins-android-emulator-emulator-did-not-appear-to-start-giving-up there is hard coded timeout constant in the plugin that results in the same issue. Someone willing to make it configurable as the other emulator properties? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37614) [android] Emulator did not appear to start; giving up
Title: Message Title Volodymyr Rudyi commented on JENKINS-37614 Re: [android] Emulator did not appear to start; giving up We recently faced this issue too. Basically, what happened in our case is that the android-jenkins-plugin started an emulator instance and didn't kill it/shutdown properly on a previous build. All future builds were failing with similar messages. But if you try to execute the command that the plugin uses to launch the AVD you will get the following error: sh-4.2$ /opt/android-sdk-linux/tools/emulator -engine classic -ports 5714,5715 -report-console tcp:5826,max=60 -prop persist.sys.language=en -prop persist.sys.country=US -avd hudson_en-US_240_FWQVGA_android-23_armeabi-v7a_test -no-snapshot-load -no-snapshot-save -no-window WARNING: Force to use classic engine to support snapshot. emulator: WARNING: Classic qemu does not support SMP. The hw.cpu.ncore option from your config file is ignored. emulator: WARNING: userdata image already in use, changes will not persist! Creating filesystem with parameters: Size: 576716800 Block size: 4096 Blocks per group: 32768 Inodes per group: 7040 Inode size: 256 Journal blocks: 2200 Label: Blocks: 140800 Block groups: 5 Reserved block group size: 39 Created filesystem with 11/35200 inodes and 4536/140800 blocks emulator: WARNING: cache image already in use, changes will not persist! Creating filesystem with parameters: Size: 69206016 Block size: 4096 Blocks per group: 32768 Inodes per group: 4224 Inode size: 256 Journal blocks: 1024 Label: Blocks: 16896 Block groups: 1 Reserved block group size: 7 Created filesystem with 11/4224 inodes and 1302/16896 blocks WARNING: SD Card image already in use: /var/lib/jenkins/.android/avd/hudson_en-US_240_FWQVGA_android-23_armeabi-v7a_test.avd/sdcard.img Snapshot storage already in use: /var/lib/jenkins/.android/avd/hudson_en-US_240_FWQVGA_android-23_armeabi-v7a_test.avd/snapshots.imgsh-4.2$ Killing the emulator process restored everything back to normal. Looks like it's the same issue Ali Elgamal is facing Add Comment
[JIRA] (JENKINS-37614) [android] Emulator did not appear to start; giving up
Title: Message Title Maciej Gąsiorowski commented on JENKINS-37614 Re: [android] Emulator did not appear to start; giving up I can't run more than one emulator on one node, I added -verbose parameter but I don't see any information. I can't configure to utilize node as much as I want Log from build: [android] Using Android SDK: /path/to/sdk $ /path/to/sdk/platform-tools/adb start-server * daemon not running. starting it now on port 5848 * * daemon started successfully * $ /path/to/sdk/platform-tools/adb start-server [android] Starting Android emulator [android] Erasing existing emulator data... $ /path/to/sdktools/emulator -engine classic -ports 5700,5701 -report-console tcp:5827,max=60 -avd Nexus_6_API23 -no-snapshot-load -no-snapshot-save -wipe-data -no-window -gpu on -verbose [android] Emulator did not appear to start; giving up [android] Stopping Android emulator $ /path/to/sdk/platform-tools/adb kill-server Archiving artifacts Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37614) [android] Emulator did not appear to start; giving up
Title: Message Title Ali Elgamal commented on JENKINS-37614 Re: [android] Emulator did not appear to start; giving up We don't get the GPU emulation error though. Here is what we see in the logs: [android] Starting Android emulator $ /home/ec2-user/jenkins/tools/android-sdk/tools/emulator -engine classic -ports 5790,5791 -report-console tcp:5813,max=60 -prop persist.sys.language=en -prop persist.sys.country=US -avd hudson_en-US_240_WVGA_android-22_armeabi-v7a -no-snapshot-load -no-snapshot-save -no-window WARNING: Force to use classic engine to support snapshot. [android] Emulator did not appear to start; giving up [android] Stopping Android emulator $ /home/ec2-user/jenkins/tools/android-sdk/platform-tools/adb kill-server emulator: WARNING: Classic qemu does not support SMP. The hw.cpu.ncore option from your config file is ignored. Creating filesystem with parameters: Size: 69206016 Block size: 4096 Blocks per group: 32768 Inodes per group: 4224 Inode size: 256 Journal blocks: 1024 Label: Blocks: 16896 Block groups: 1 Reserved block group size: 7 Created filesystem with 11/4224 inodes and 1302/16896 blocks emulator: warning: opening audio output failed emulator: WARNING: Requested adb port (5791) is outside the recommended range [,5586]. ADB may not function properly for the emulator. See -help-port for details. emulator: Listening for console connections on port: 5790 emulator: Serial number of this emulator (for ADB): emulator-5790 [android-lint] Collecting Android Lint files... [android-lint] Finding all files that match the pattern **/lint-results*.xml [android-lint] Computing warning deltas based on reference build #325 Recording test results ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? Finished: NOT_BUILT Add Comment This message was
[JIRA] (JENKINS-37614) [android] Emulator did not appear to start; giving up
Title: Message Title Ali Elgamal commented on JENKINS-37614 Re: [android] Emulator did not appear to start; giving up We faced exactly the same over here. It is an intermittent problem though, sometime occurs and sometimes not but it happens pretty frequently. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37614) [android] Emulator did not appear to start; giving up
Title: Message Title dan vin created an issue Jenkins / JENKINS-37614 [android] Emulator did not appear to start; giving up Issue Type: Bug Assignee: Christopher Orr Components: android-emulator-plugin Created: 2016/Aug/23 7:52 AM Priority: Blocker Reporter: dan vin After updating the sdk i started getting the following eerror: $ /Users/buildagent/builds/tools/android-sdk/tools/android list target [android] Using Android SDK: /Users/buildagent/builds/tools/android-sdk [android] Setting hardware properties: vm.heapSize: 1024 vm.ramSize: 1024 $ /Users/buildagent/builds/tools/android-sdk/platform-tools/adb start-server daemon not running. starting it now on port 5848 * daemon started successfully * $ /Users/buildagent/builds/tools/android-sdk/platform-tools/adb start-server [android] Starting Android emulator $ /Users/buildagent/builds/tools/android-sdk/tools/emulator -engine classic -ports 5760,5761 -report-console tcp:5817,max=60 -prop persist.sys.language=en -prop persist.sys.country=US -avd hudson_en-US_480_1080x1920_android-23_armeabi-v7a_nexus5 -no-snapshot-load -no-snapshot-save -no-window emulator: WARNING: Increasing RAM size to 1024MB emulator: ERROR: GPU emulation is disabled. Only screen size of 768 X 1280 or smaller is supported when GPU emulation is disabled. [android] Emulator did not appear to start; giving up [android] Stopping Android emulator This makes it impossible to continue and run the tests. It used to work untill recently we updated the sdk.
