search

pitate7777777 / maven-android-plugin

Automatically exported from code.google.com/p/maven-android-plugin
0 stars 0 forks source link

Emulator is not "ready to use" after emulator-start #462

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. execute emulator-start goal.
2. execute instrumentation test
3.

What is the expected output?
The test will run since the device is ready for use.

What do you see instead?
The device is offline.

What version of maven-android-plugin are you using?
3.8.2

What are the complete output lines of "mvn -version" on your machine?
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 
18:22:22+0300)
Maven home: C:\Users\xxxx\Work\Maven\apache-maven-3.1.1\bin\..
Java version: 1.7.0_25, vendor: Oracle Corporation
Java home: c:\Program Files\Java\jdk1.7.0_25\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"

Please provide any additional information below.
I noticed that in AbstractEmulatorMojo in waitUntilDeviceIsConnectedOrTimeout 
there is a line (273) myEmulator.isOnline() which decides if the emulator is 
connected.

I think that this might be problematic since the method will return true when 
the device is present (adb devices will show the device) but not when it is 
actually ready to use.

The funny thing is that there is a script wait_for_emulator in the project 
which handle exactly that.. 

In other words, the project CI doesn't 'eat its own dog food' and has it's own 
script instead of building the emulator using the emulator-start goal.

I think that it's more correct to decide that a device is online only after 
"$bootanim" =~ "stopped"

Original issue reported on code.google.com by ikabar on 1 May 2014 at 8:19

GoogleCodeExporter commented 9 years ago 
Is that a pull request I hearing forming?

Original comment by william....@xandar.com.au on 1 May 2014 at 9:28

GoogleCodeExporter commented 9 years ago 
We just never got around to fix this in the ci and in general. Pull request 
certainly welcome..

Original comment by mosa...@gmail.com on 15 May 2014 at 4:18

GoogleCodeExporter commented 9 years ago 
We are no longer using the issue tracking system on Google Code. Please refile 
this issue on https://github.com/jayway/maven-android-plugin/issues if you 
still have this problem with the latest release of the Android Maven Plugin

Original comment by mosa...@gmail.com on 19 May 2014 at 4:20