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

Emulator occasionally hangs indefinitely on startup, unable to connect adb

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • android-emulator-plugin
    • None
    • Android-Emulator 1.19-SNAPSHOT (from git)
      Jenkins 1.438
      SDK r15

      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.

          [JENKINS-11952] Emulator occasionally hangs indefinitely on startup, unable to connect adb

          Jørgen Tjernø created issue -
          Jørgen Tjernø made changes -
          Description Original: 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.           		New: 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.
          Christopher Orr made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]
          Roberto Andrade made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Closed [ 6 ] New: Reopened [ 4 ]
          Richard Mortimer made changes -
          Assignee Original: Christopher Orr [ orrc ] New: Richard Mortimer [ oldelvet ]
          Oskar Danielsson made changes -
          Link New: This issue is related to JENKINS-23735 [ JENKINS-23735 ]
          Christopher Orr made changes -
          Link New: This issue is duplicated by JENKINS-25790 [ JENKINS-25790 ]
          Christopher Orr made changes -
          Assignee Original: Richard Mortimer [ oldelvet ] New: Christopher Orr [ orrc ]
          Resolution New: Fixed [ 1 ]
          Status Original: Reopened [ 4 ] New: Resolved [ 5 ]
          Christopher Orr made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          Christopher Orr made changes -
          Link New: This issue is duplicated by JENKINS-24817 [ JENKINS-24817 ]
          Andy Piper made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Closed [ 6 ] New: Reopened [ 4 ]

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

              Created:
              Updated: