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
    • 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

            Activity

            jorgenpt Jørgen Tjernø created issue -
            jorgenpt Jørgen Tjernø made changes -
            Field Original Value New Value
            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:
            {code} $ /opt/android-sdk/platform-tools/adb connect emu:38996,48597
              $ /opt/android-sdk/platform-tools/adb -s emulator-38996 shell getprop dev.bootcomplete{code}

            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.
            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:
            {code}$ /opt/android-sdk/platform-tools/adb connect emu:38996,48597
            $ /opt/android-sdk/platform-tools/adb -s emulator-38996 shell getprop dev.bootcomplete{code}

            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.
            orrc Christopher Orr made changes -
            Status Open [ 1 ] Closed [ 6 ]
            Resolution Fixed [ 1 ]
            randroid Roberto Andrade made changes -
            Resolution Fixed [ 1 ]
            Status Closed [ 6 ] Reopened [ 4 ]
            oldelvet Richard Mortimer made changes -
            Assignee Christopher Orr [ orrc ] Richard Mortimer [ oldelvet ]
            oskard Oskar Danielsson made changes -
            Link This issue is related to JENKINS-23735 [ JENKINS-23735 ]
            orrc Christopher Orr made changes -
            Link This issue is duplicated by JENKINS-25790 [ JENKINS-25790 ]
            orrc Christopher Orr made changes -
            Status Reopened [ 4 ] Resolved [ 5 ]
            Assignee Richard Mortimer [ oldelvet ] Christopher Orr [ orrc ]
            Resolution Fixed [ 1 ]
            orrc Christopher Orr made changes -
            Status Resolved [ 5 ] Closed [ 6 ]
            orrc Christopher Orr made changes -
            Link This issue is duplicated by JENKINS-24817 [ JENKINS-24817 ]
            andyp1per Andy Piper made changes -
            Resolution Fixed [ 1 ]
            Status Closed [ 6 ] Reopened [ 4 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 142224 ] JNJira + In-Review [ 186030 ]

              People

              • Assignee:
                orrc Christopher Orr
                Reporter:
                jorgenpt Jørgen Tjernø
              • Votes:
                10 Vote for this issue
                Watchers:
                22 Start watching this issue

                Dates

                • Created:
                  Updated: