|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" 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.
I extended my patch series to capture logcat output irrespective of whether boot completes or not. The change was quite simple although I did have to put a short delay in to allow the logcat output to be captured before the emulator was killed after a failed boot.
A test build can be downloaded from
android-emulator-2.12-SNAPSHOT.hpi
Pull request at
https://github.com/jenkinsci/android-emulator-plugin/pull/39
Note the pull request still contains the devices -l output. For now I think that will be useful in diagnosing the various causes of boot failures that may be out there. I'm not sure whether it just makes the logs too messy to be included long term.
I'm also considering getting rid of the connect and disconnect operations. I don't think they add anything to the robustness of startup now we are using the emulator-xxxx style device name.