-
Bug
-
Resolution: Incomplete
-
Major
-
None
-
Fedora Linux i686, Hudson ver. 1.396, Android Emulator Plugin v. 1.6, Xvnc + Xvnc Plugin (setup as described in http://groups.google.com/group/robotium-developers/browse_thread/thread/af0cce19514e4018/029953a677a81bd6)
I am trying to create an avd using the android emulator plugin ("Run emulator with properties" option) but I receive an error stating "Could not create Android emulator: Failed to run AVD creation command." I am unsure how to trouble shoot this problem as everything appears to be set up correctly according to the wiki page. Here is the log:
Starting xvnc
[workspace] $ Xvnc :58 -localhost -geometry 1280x1024 -depth 24 -SecurityTypes None
[android] Using Android SDK: /var/android/android-sdk-linux_x86/
[android] Creating Android AVD at /.android/avd/hudson_en-US_160_HVGA_android-4.avd
[android] Failed to run AVD creation command
[android] Could not create Android emulator: Failed to run AVD creation command
Terminating xvnc.
Xvnc Free Edition 4.1.2
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Underlying X server release 10300000, The X.Org Foundation
Sun May 8 09:49:00 2011
vncext: VNC extension running!
vncext: Listening for VNC connections on port 5958
vncext: created VNC server for screen 0
Finished: NOT_BUILT
I tracked down where this is failing in the code to https://github.com/jenkinsci/android-emulator-plugin/blob/master/src/main/java/hudson/plugins/android_emulator/EmulatorConfig.java#L463 . We also ran "android create avd -c 32M -s 320x480 -n hudson_en-US_160_HVGA_android-4 -t 2" from the command line and it works fine (prompted for a create custom hardware profile though). Unfortunately, this was not enough information to figure out what is wrong. A corollary to this problem is that the android emulator plugin should have the option to run android creation commands with the -v (verbosity) turned on as described by http://developer.android.com/guide/developing/tools/android.html.
To recap, I think this "failed to run AVD creation command" is a bug with how Android Emulator Plugin uses the creation command. I also felt logging the -v option would have been tremendously helpful for troubleshooting. I can log this portion as a separate enhancement if need be.
Thanks and please let me know if I can provide any more information.