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

adb daemon killed after job complete breaks other running emulators

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Labels:
      None
    • Environment:
      SDK Tools r11, Fedora Core 14 i686 (slave), number of executors per slave 4. Jenkins 1.414, Android Emulator 1.15
    • Similar Issues:

      Description

      When running multiple emulator instances on a single node each within their own Xvnc session, at the end of the job the plugin seems to end up killing the adb daemon. The other emulators lose connection to the daemon, and even though a background task may start adb again, emulators may not successfully reconnect to adb. This is particularly problematic when running large multi-configuration android-emulator jobs on a single node with a large degree of parallelism. 2 concurrent executors seems to occasionally cause problems but with 4 the results are not even worthwhile to review.

      Reducing the number of executors on the node to 1 (or otherwise weighting the job to consume an entire system) does work-around the problem.

        Attachments

          Activity

            People

            • Assignee:
              orrc Christopher Orr
              Reporter:
              hokatichen Mike Elkin
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: