[JIRA] (JENKINS-12120) Emulator startup shouldn't fail when .ini is missing
[
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
[JIRA] (JENKINS-12120) Emulator startup shouldn't fail when .ini is missing
[
https://issues.jenkins-ci.org/browse/JENKINS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160696#comment-160696
]
dogfood commented on JENKINS-12120:
---
Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png!
[plugins_android-emulator
#28|http://ci.jenkins-ci.org/job/plugins_android-emulator/28/]
[FIXED JENKINS-12120] Check for config.ini before starting or after
creating AVD. (Revision 21b1693bafc80a989a31f7b08290f9492ed1d4c1)
Result = SUCCESS
Christopher Orr :
Files :
* src/main/java/hudson/plugins/android_emulator/EmulatorConfig.java
> 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
[JIRA] (JENKINS-12120) Emulator startup shouldn't fail when .ini is missing
[
https://issues.jenkins-ci.org/browse/JENKINS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SCM/JIRA link daemon resolved JENKINS-12120.
Resolution: Fixed
> 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
[JIRA] (JENKINS-12120) Emulator startup shouldn't fail when .ini is missing
[
https://issues.jenkins-ci.org/browse/JENKINS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160693#comment-160693
]
SCM/JIRA link daemon commented on JENKINS-12120:
Code changed in jenkins
User: Christopher Orr
Path:
src/main/java/hudson/plugins/android_emulator/EmulatorConfig.java
http://jenkins-ci.org/commit/android-emulator-plugin/21b1693bafc80a989a31f7b08290f9492ed1d4c1
Log:
[FIXED JENKINS-12120] Check for config.ini before starting or after creating
AVD.
Also show error output if AVD creation fails for some unknown reason.
This allows the plugin to detect and recover from incorrectly-created AVDs;
existing AVDs found without a config.ini file will be replaced with a new AVD.
> 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
[JIRA] (JENKINS-12120) Emulator startup shouldn't fail when .ini is missing
[
https://issues.jenkins-ci.org/browse/JENKINS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160632#comment-160632
]
francisdb commented on JENKINS-12120:
-
I found the issue
{code}
/opt/android-sdk-linux/tools/android create avd -a -c 16M -s WVGA -n
hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7.avd -t "Google Inc.:Google
APIs:7"
Valid skins: WVGA854, WQVGA400, HVGA, WQVGA432, QVGA, WVGA800 (default)
Error: 'WVGA' is not a valid skin name or size (NNNxMMM)
{code}
After that I tried this on the console:
{code}
/opt/android-sdk-linux/tools/android create avd -a -c 16M -s WVGA800 -n
hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7.avd -t "Google Inc.:Google
APIs:7"
Auto-selecting single ABI armeabi
Error: Unable to find a
'/opt/android-sdk-linux/tools/lib/emulator/snapshots.img' file to copy into the
AVD folder.
{code}
This was a permission issue where the folder was not accessible (missing +x
persmission).
Could you make sure the plugin shows the error output in the future?
> 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
[JIRA] (JENKINS-12120) Emulator startup shouldn't fail when .ini is missing
[
https://issues.jenkins-ci.org/browse/JENKINS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160562#comment-160562
]
Christopher Orr commented on JENKINS-12120:
---
The command used for that AVD would be (assuming an SD card of 16MB):
{{android create avd -a -c 16M -s WVGA -n
hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7.avd -t "Google Inc.:Google
APIs:7"}}
> 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
[JIRA] (JENKINS-12120) Emulator startup shouldn't fail when .ini is missing
[
https://issues.jenkins-ci.org/browse/JENKINS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160544#comment-160544
]
francisdb commented on JENKINS-12120:
-
Nothing I can do to debug this?
> 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
[JIRA] (JENKINS-12120) Emulator startup shouldn't fail when .ini is missing
[
https://issues.jenkins-ci.org/browse/JENKINS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160034#comment-160034
]
francisdb commented on JENKINS-12120:
-
Have not found any avd, could you tell me the command used by the plugin to
create the avd so I can try to reproduce this?
> 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
[JIRA] (JENKINS-12120) Emulator startup shouldn't fail when .ini is missing
[
https://issues.jenkins-ci.org/browse/JENKINS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160031#comment-160031
]
Christopher Orr commented on JENKINS-12120:
---
Can you check if "hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7.avd" was
created *anywhere* on disk, not just in /var/lib/jenkins/.android/avd?
Sometimes there can be a conflict between where the plugin looks for AVDs and
where the `android` tool creates them.
> 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
[JIRA] (JENKINS-12120) Emulator startup shouldn't fail when .ini is missing
[
https://issues.jenkins-ci.org/browse/JENKINS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160026#comment-160026
]
francisdb edited comment on JENKINS-12120 at 3/8/12 2:59 PM:
-
Logs look similar, nothing mentioned about creating the avd failing, and the
command used is not logged, otherwise I could try it manually.
{code}
Checking out Revision f8d74574069d0aac99890ca930a166c948729f6b (origin/HEAD,
origin/master)
Warning : There are multiple branch changesets here
$ /opt/android-sdk-linux/tools/android list target
[android] Using Android SDK: /opt/android-sdk-linux
[android] Creating Android AVD:
/var/lib/jenkins/.android/avd/hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7.avd
$ /opt/android-sdk-linux/platform-tools/adb start-server
[android] Starting Android emulator
$ /opt/android-sdk-linux/tools/emulator -no-boot-anim -ports 55292,32849 -prop
persist.sys.language=en -prop persist.sys.country=US -avd
hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7 -no-snapshot-load
-no-snapshot-save -no-window -logcat *:d
PANIC: Could not open:
/var/lib/jenkins/.android/avd/hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7.ini*
daemon not running. starting it now on port 33012 *
* daemon started successfully *
[android] Emulator did not appear to start; giving up
$ /opt/android-sdk-linux/platform-tools/adb disconnect localhost:32849
[android] Stopping Android emulator
$ /opt/android-sdk-linux/platform-tools/adb kill-server
Recording test results
No test report files were found. Configuration error?
Emma: looking for coverage reports in the provided path:
**/coverage/coverage*.xml
Finished: NOT_BUILT
{code}
was (Author: francisdb):
Logs look similar, nothing mentioned about creating the avd failing, and
the command used is not logged, otherwise I could try it manually.
Checking out Revision f8d74574069d0aac99890ca930a166c948729f6b (origin/HEAD,
origin/master)
Warning : There are multiple branch changesets here
$ /opt/android-sdk-linux/tools/android list target
[android] Using Android SDK: /opt/android-sdk-linux
[android] Creating Android AVD:
/var/lib/jenkins/.android/avd/hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7.avd
$ /opt/android-sdk-linux/platform-tools/adb start-server
[android] Starting Android emulator
$ /opt/android-sdk-linux/tools/emulator -no-boot-anim -ports 55292,32849 -prop
persist.sys.language=en -prop persist.sys.country=US -avd
hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7 -no-snapshot-load
-no-snapshot-save -no-window -logcat *:d
PANIC: Could not open:
/var/lib/jenkins/.android/avd/hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7.ini*
daemon not running. starting it now on port 33012 *
* daemon started successfully *
[android] Emulator did not appear to start; giving up
$ /opt/android-sdk-linux/platform-tools/adb disconnect localhost:32849
[android] Stopping Android emulator
$ /opt/android-sdk-linux/platform-tools/adb kill-server
Recording test results
No test report files were found. Configuration error?
Emma: looking for coverage reports in the provided path:
**/coverage/coverage*.xml
Finished: NOT_BUILT
> 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
[JIRA] (JENKINS-12120) Emulator startup shouldn't fail when .ini is missing
[
https://issues.jenkins-ci.org/browse/JENKINS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160026#comment-160026
]
francisdb commented on JENKINS-12120:
-
Logs look similar, nothing mentioned about creating the avd failing, and the
command used is not logged, otherwise I could try it manually.
Checking out Revision f8d74574069d0aac99890ca930a166c948729f6b (origin/HEAD,
origin/master)
Warning : There are multiple branch changesets here
$ /opt/android-sdk-linux/tools/android list target
[android] Using Android SDK: /opt/android-sdk-linux
[android] Creating Android AVD:
/var/lib/jenkins/.android/avd/hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7.avd
$ /opt/android-sdk-linux/platform-tools/adb start-server
[android] Starting Android emulator
$ /opt/android-sdk-linux/tools/emulator -no-boot-anim -ports 55292,32849 -prop
persist.sys.language=en -prop persist.sys.country=US -avd
hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7 -no-snapshot-load
-no-snapshot-save -no-window -logcat *:d
PANIC: Could not open:
/var/lib/jenkins/.android/avd/hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7.ini*
daemon not running. starting it now on port 33012 *
* daemon started successfully *
[android] Emulator did not appear to start; giving up
$ /opt/android-sdk-linux/platform-tools/adb disconnect localhost:32849
[android] Stopping Android emulator
$ /opt/android-sdk-linux/platform-tools/adb kill-server
Recording test results
No test report files were found. Configuration error?
Emma: looking for coverage reports in the provided path:
**/coverage/coverage*.xml
Finished: NOT_BUILT
> 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
[JIRA] (JENKINS-12120) Emulator startup shouldn't fail when .ini is missing
[
https://issues.jenkins-ci.org/browse/JENKINS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160024#comment-160024
]
Christopher Orr commented on JENKINS-12120:
---
Sounds like a different bug.
Can you paste more of the console output somewhere; in a new bug if you're not
seeing the "PANIC: Could not open ... .ini" message?
> 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
[JIRA] (JENKINS-12120) Emulator startup shouldn't fail when .ini is missing
[
https://issues.jenkins-ci.org/browse/JENKINS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160011#comment-160011
]
francisdb commented on JENKINS-12120:
-
It seems that the emulator is not created at all
[android] Using Android SDK: /opt/android-sdk-linux
[android] Creating Android AVD:
/var/lib/jenkins/.android/avd/hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7.avd
/var/lib/jenkins/.android/avd is empty
> 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
[JIRA] (JENKINS-12120) Emulator startup shouldn't fail when .ini is missing
[
https://issues.jenkins-ci.org/browse/JENKINS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160001#comment-160001
]
Christopher Orr commented on JENKINS-12120:
---
Did this happen to an existing emulator, or was it created during the build
where you saw this error?
Probably you can delete the emulator and try again.
> 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
[JIRA] (JENKINS-12120) Emulator startup shouldn't fail when .ini is missing
[
https://issues.jenkins-ci.org/browse/JENKINS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159996#comment-159996
]
francisdb commented on JENKINS-12120:
-
Is there a workaround for this issue?
> 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
