[
https://issues.jenkins-ci.org/browse/JENKINS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Orr closed JENKINS-12120.
-------------------------------------
This has been released in version 2.2 of the plugin.
> Emulator startup shouldn't fail when .ini is missing
> ----------------------------------------------------
>
> Key: JENKINS-12120
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12120
> Project: Jenkins
> Issue Type: Bug
> Components: android-emulator
> Reporter: Jørgen Tjernø
> Assignee: Christopher Orr
>
> {noformat}
> 17:14:47 [android] Starting Android emulator
> 17:14:47 [android] Erasing existing emulator data...
> 17:14:47 $ /Users/buildserver/Android/sdk/tools/emulator -no-boot-anim
> -ports 58108,58109 -prop persist.sys.language=en -prop persist.sys.country=US
> -avd hudson_en-US_160_841x490_android-7 -no-snapshot-load -no-snapshot-save
> -wipe-data -no-window -no-snapshot-update-time
> 17:14:50 PANIC: Could not open:
> /tmp/jenkins-root-ssh/workspace/client_android_staging_test/.android/avd/hudson_en-US_160_841x490_android-7.ini*
> daemon not running. starting it now on port 58110 *
> 17:14:50 * daemon started successfully *
> 17:15:52 [android] Emulator did not appear to start; giving up
> {noformat}
> I'm guessing the code tests for a .avd but not a .ini - I don't know how my
> machine managed to end up with only a .avd (I checked, and it existed), but
> in that scenario, the plugin should probably recreate the emulator (android
> create avd -f).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
