I have a strange situation with Jenkins when trying to run the tests.

The configuration of the job clearly specifies to run the tests on this specific avd: &quot;**hudson_en-US_160_HVGA_android-18_armeabi-v7a**&quot;, 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 &quot;**unknown-sdk**&quot;.

![enter image description here][1]

The tests are successfully executed on the specific avd, and fail on &quot;unknown-sdk&quot;:

The relevant portion of the log:

&gt; [SR.runTests] Executing instrumentation suite on 2
&gt; device(s).   
&gt; [SR.runTests] [emulator-8215] Starting
&gt; execution.   
&gt; [SR.runTests] [localhost:8216] Starting
&gt; execution.
&gt; 
&gt; Running am instrument -w -r  -e class com.smoke.tests.LoginTest
&gt; com.muume.dev.test/android.support.test.runner.AndroidJUnitRunner on
&gt; unknown-sdk-localhost:8216
&gt; 
&gt; 2015-06-17 11:54:05 [SDR.printStream] [localhost:8216] STDOUT 11:54:05
&gt; I/InstrumentationResultParser: test run failed: &#39;Unable to find
&gt; instrumentation info for:
&gt; ComponentInfo{com.muume.dev.test/android.support.test.runner.AndroidJUnitRunner}

As you can see, it detected 2 devices: **emulator-8215** which is the known avd, and **localhost-8216** which is the unknown and causes the problems.

My question is how to restrict the tests to run only one single emulator, and from where did the &quot;unknown-sdk-localhost&quot; comes from.



  [1]: http://i.stack.imgur.com/u4AZv.png

All Spoon Gradle-Plugin Solutions on Gang of Coders

Total of 1 Spoon Gradle-Plugin Solutions

"unknown-sdk" device when executing tests in Jenkins