Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-37614

[android] Emulator did not appear to start; giving up

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      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.

        Attachments

          Activity

          Hide
          lz1asl lz1asl added a comment -

          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?

          Show
          lz1asl lz1asl added a comment - 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?
          Hide
          lz1asl lz1asl added a comment -

          There is a pull request pending https://github.com/jenkinsci/android-emulator-plugin/pull/63, please have a look.
          Many thanks to ikolomiyets.

          Show
          lz1asl lz1asl added a comment - There is a pull request pending https://github.com/jenkinsci/android-emulator-plugin/pull/63 , please have a look. Many thanks to ikolomiyets.
          Hide
          balakamath bala kamath added a comment -

          Even i am facing same issue: Jenkins 2.38. AndroidEmultorPlugin version: 2.15.
          when will this change be available? and which version?

          Show
          balakamath bala kamath added a comment - Even i am facing same issue: Jenkins 2.38. AndroidEmultorPlugin version: 2.15. when will this change be available? and which version?
          Hide
          timon Jun Liu added a comment -

          Meet the same issue, the emulator was specified random ports, usually start with 57xx, which is out of adb supported range (5554-5584)

           

          `emulator –help-port` may describe the details

           

          And there is no config option to force specify the ports or integrate with port-allocator-plugin

           

          Even force set the `emulator options` with -port or -ports, it may not works expectly

          e.g. pass emulator options with -port 5554, when the plugin have launch the emulator, I can ssh to the slave and use `netstat -ant` to check the emulator already in running and listen on port 5554 and 5555, but the plugin still polling with `adb -s emulator-XXXX wait-for-device` till timeout.

           

          Show
          timon Jun Liu added a comment - Meet the same issue, the emulator was specified random ports, usually start with 57xx, which is out of adb supported range (5554-5584)   `emulator –help-port` may describe the details   And there is no config option to force specify the ports or integrate with port-allocator-plugin   Even force set the `emulator options` with -port or -ports, it may not works expectly e.g. pass emulator options with -port 5554, when the plugin have launch the emulator, I can ssh to the slave and use `netstat -ant` to check the emulator already in running and listen on port 5554 and 5555, but the plugin still polling with `adb -s emulator-XXXX wait-for-device` till timeout.  
          Hide
          ganeshvrbhat Ganesh Bhat added a comment -

          Agree with Jun Liu. I'm also facing same problem. Any workaround for this issue? 

          Show
          ganeshvrbhat Ganesh Bhat added a comment - Agree with Jun Liu . I'm also facing same problem. Any workaround for this issue? 

            People

            • Assignee:
              orrc Christopher Orr
              Reporter:
              danvin dan vin
            • Votes:
              5 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated: