title: "unknown-sdk" device when executing tests in Jenkins
body: <p>I have a strange situation with Jenkins when trying to run the tests.</p>
  
  <p>The configuration of the job clearly specifies to run the tests on this specific avd: "<strong>hudson_en-US_160_HVGA_android-18_armeabi-v7a</strong>", but for some odd reasons, during the build process, 2 devices are found. One of the devices is the previous one, but the other is called "<strong>unknown-sdk</strong>".</p>
  
  <p><img src="https://i.stack.imgur.com/u4AZv.png" alt="enter image description here"></p>
  
  <p>The tests are successfully executed on the specific avd, and fail on "unknown-sdk":</p>
  
  <p>The relevant portion of the log:</p>
  
  <blockquote>
    <p>[SR.runTests] Executing instrumentation suite on 2
    device(s).<br>
    [SR.runTests] [emulator-8215] Starting
    execution.<br>
    [SR.runTests] [localhost:8216] Starting
    execution.</p>
    
    <p>Running am instrument -w -r  -e class com.smoke.tests.LoginTest
    com.muume.dev.test/android.support.test.runner.AndroidJUnitRunner on
    unknown-sdk-localhost:8216</p>
    
    <p>2015-06-17 11:54:05 [SDR.printStream] [localhost:8216] STDOUT 11:54:05
    I/InstrumentationResultParser: test run failed: 'Unable to find
    instrumentation info for:
    ComponentInfo{com.muume.dev.test/android.support.test.runner.AndroidJUnitRunner}</p>
  </blockquote>
  
  <p>As you can see, it detected 2 devices: <strong>emulator-8215</strong> which is the known avd, and <strong>localhost-8216</strong> which is the unknown and causes the problems.</p>
  
  <p>My question is how to restrict the tests to run only one single emulator, and from where did the "unknown-sdk-localhost" comes from.</p>