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

Emulator occasionally hangs indefinitely on startup, unable to connect adb

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Reopened (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: android-emulator-plugin
    • Labels:
      None
    • Environment:
      Android-Emulator 1.19-SNAPSHOT (from git)
      Jenkins 1.438
      SDK r15
    • Similar Issues:

      Description

      Sometimes the emulator will fail to start up, this seems to only (or mostly) happen when snapshots are enabled. When this happens, it'll go in a loop of, until it times out:

      $ /opt/android-sdk/platform-tools/adb connect emu:38996,48597
$ /opt/android-sdk/platform-tools/adb -s emulator-38996 shell getprop dev.bootcomplete

      This seems to be because sometimes the adb server never moves the device from the "offline" to the "online" status. Forcing a reconnect seems to fix this - like restarting the adb server.

        Attachments

          Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-25790 New adb connect command always fails to connect emulator on OS X

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-24817 Android emulator timeout during launch for 4.4 emulators

          • Major - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-23735 Emulator plugin first time build "adb start-server" times out after 5 seconds

          • Major - Major loss of function.
          • Closed

            Activity

            Ascending order - Click to sort in descending order
            78 older comments
            Hide
            Permalink
            jhansche Joe Hansche added a comment -

            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.

            Show
            jhansche Joe Hansche added a comment - 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.
            Hide
            Permalink
            orrc Christopher Orr added a comment -

            Version 2.13 of the plugin has been released, which includes the updates discussed here.

            Show
            orrc Christopher Orr added a comment - Version 2.13 of the plugin has been released, which includes the updates discussed here.
            Hide
            Permalink
            orrc Christopher Orr added a comment -

            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.

            Show
            orrc Christopher Orr added a comment - 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.
            Hide
            Permalink
            andyp1per Andy Piper added a comment -

            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

            Show
            andyp1per Andy Piper added a comment - 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
            Hide
            Permalink
            andyp1per Andy Piper added a comment -

            Does not work on current android releases.

            Android Debug Bridge version 1.0.32
            Revision 57224c5cff69-android

            Show
            andyp1per Andy Piper added a comment - Does not work on current android releases. Android Debug Bridge version 1.0.32 Revision 57224c5cff69-android

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              jorgenpt Jørgen Tjernø
              Votes:
              10 Vote for this issue
              Watchers:
              22 Start watching this issue

                Dates

                Created:
                Updated: