Hmm... I'm seeing a very similar issue on my Jenkins CI server whereby the connectedCheck task fails because of the same "Unable to find instrumentation info for: ComponentInfo" error that you are seeing. For me the tests run just fine on the emulator on my local machine. I'm wondering if this is also the case for your build?
On Wednesday, April 9, 2014 7:18:17 PM UTC-5, [email protected] wrote: > > > We used the Android Gradle plugin to build our projects on Jenkins, but we > actually have a failure on 'Process crashed', but the Jenkins still > reported as a success. I believe this doesn't output any non-zero exit code > to Jenkins right? > > Is this a bug or something we need to get a workaround for this? > > > > > *2014-04-08 15:38:34* : >> *connectedAndroidTest**2014-04-08 15:38:34* Executing task >> ':connectedAndroidTest' (up-to-date check took 0.0 secs) due to: >> *2014-04-08 15:38:34* Task has not declared any outputs. >> *2014-04-08 15:39:03* Starting 0 tests on sdk - 2.3.3 >> *2014-04-08 15:39:03* Tests on sdk - 2.3.3 failed: Instrumentation run >> failed due to 'Process crashed.' >> *2014-04-08 15:39:06* Starting 0 tests on emulator-37273 - 2.3.3 >> *2014-04-08 15:39:06* Tests on emulator-37273 - 2.3.3 failed: Unable to >> find instrumentation info for: >> ComponentInfo{com.lookout.androidsecurity.test/android.test.InstrumentationTestRunner} >> *2014-04-08 15:39:07* :*connectedAndroidTest* (Thread[Daemon,5,main]) >> completed. Took 33.728 secs. >> *2014-04-08 15:39:07* :*preReleaseBuild* (Thread[Daemon,5,main]) started. >> *2014-04-08 15:39:07* :*preReleaseBuild* > > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
