[JIRA] (JENKINS-14901) Emulator start failed on Ubuntu (SDK 20.0.3)
recampbell commented on JENKINS-14901 Emulator start failed on Ubuntu (SDK 20.0.3) We were having this precise issue. As indicated by this stackoverflow thread, we fixed the issue by setting the LD_LIBRARY_PATH as follows (using EnvInject): LD_LIBRARY_PATH=/opt/android/android-sdk-linux/tool/lib I think the fix is for the Android Emulator plugin to populate this for us? 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14901) Emulator start failed on Ubuntu (SDK 20.0.3)
Matti Linnanvuori commented on JENKINS-14901 Emulator start failed on Ubuntu (SDK 20.0.3) I have this issue intermittently even after linking emulator to emulator-arm. The emulator processes keep piling up because the plugin does not kill them after unsuccessfully trying to connect to them. Building remotely on madmax2 in workspace /var/lib/jenkins/projects/avt/tests Starting xvnc tests $ vncserver :11 -localhost -nolisten tcp New 'X' desktop is madmax2.ecolane.com:11 Starting applications specified in /var/lib/jenkins/.vnc/xstartup Log file is /var/lib/jenkins/.vnc/madmax2.ecolane.com:11.log android Using Android SDK: /opt/adt-bundle-linux-x86_64/sdk android Waiting 1 seconds before starting emulator... $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb start-server android Starting Android emulator $ /opt/adt-bundle-linux-x86_64/sdk/tools/emulator -no-boot-anim -ports 56341,34347 -avd Android2.2GoogleAPIs -no-snapshot-load -no-snapshot-save daemon not running. starting it now on port 50229 * daemon started successfully * android Emulator did not appear to start; giving up $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb disconnect localhost:34347 android Stopping Android emulator $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb kill-server Taking screenshot. tests $ import -window root -display :11 screenshot.jpg Terminating xvnc. $ vncserver -kill :11 Killing Xtightvnc process ID 18436 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
[JIRA] (JENKINS-14901) Emulator start failed on Ubuntu (SDK 20.0.3)
Matti Linnanvuori edited a comment on JENKINS-14901 Emulator start failed on Ubuntu (SDK 20.0.3) I have this issue intermittently even after linking emulator to emulator-arm. The emulator processes keep piling up because the plugin does not kill them after unsuccessfully trying to connect to them. I have tried to fix the issue by building a private version of the plugin with setting the ignore variable to true even for UNIX but it did not help. Building remotely on madmax2 in workspace /var/lib/jenkins/projects/avt/tests Starting xvnc tests $ vncserver :11 -localhost -nolisten tcp New 'X' desktop is madmax2.ecolane.com:11 Starting applications specified in /var/lib/jenkins/.vnc/xstartup Log file is /var/lib/jenkins/.vnc/madmax2.ecolane.com:11.log android Using Android SDK: /opt/adt-bundle-linux-x86_64/sdk android Waiting 1 seconds before starting emulator... $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb start-server android Starting Android emulator $ /opt/adt-bundle-linux-x86_64/sdk/tools/emulator -no-boot-anim -ports 56341,34347 -avd Android2.2GoogleAPIs -no-snapshot-load -no-snapshot-save daemon not running. starting it now on port 50229 * daemon started successfully * android Emulator did not appear to start; giving up $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb disconnect localhost:34347 android Stopping Android emulator $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb kill-server Taking screenshot. tests $ import -window root -display :11 screenshot.jpg Terminating xvnc. $ vncserver -kill :11 Killing Xtightvnc process ID 18436 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
[JIRA] (JENKINS-14901) Emulator start failed on Ubuntu (SDK 20.0.3)
Matti Linnanvuori edited a comment on JENKINS-14901 Emulator start failed on Ubuntu (SDK 20.0.3) I have this issue intermittently even after linking emulator to emulator-arm. The emulator processes keep piling up because the plugin does not kill them after unsuccessfully trying to connect to them. I have tried to fix the issue by building a private version of the plugin with setting the ignore variable to true even for UNIX but it did not help. My environment is Xen Linux 3.2.0-3-amd64 #1 SMP 86_64 Debian GNU/Linux wheezy/sid. Building remotely on madmax2 in workspace /var/lib/jenkins/projects/avt/tests Starting xvnc tests $ vncserver :11 -localhost -nolisten tcp New 'X' desktop is madmax2.ecolane.com:11 Starting applications specified in /var/lib/jenkins/.vnc/xstartup Log file is /var/lib/jenkins/.vnc/madmax2.ecolane.com:11.log android Using Android SDK: /opt/adt-bundle-linux-x86_64/sdk android Waiting 1 seconds before starting emulator... $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb start-server android Starting Android emulator $ /opt/adt-bundle-linux-x86_64/sdk/tools/emulator -no-boot-anim -ports 56341,34347 -avd Android2.2GoogleAPIs -no-snapshot-load -no-snapshot-save daemon not running. starting it now on port 50229 * daemon started successfully * android Emulator did not appear to start; giving up $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb disconnect localhost:34347 android Stopping Android emulator $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb kill-server Taking screenshot. tests $ import -window root -display :11 screenshot.jpg Terminating xvnc. $ vncserver -kill :11 Killing Xtightvnc process ID 18436 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
[JIRA] (JENKINS-14901) Emulator start failed on Ubuntu (SDK 20.0.3)
Matti Linnanvuori edited a comment on JENKINS-14901 Emulator start failed on Ubuntu (SDK 20.0.3) I have this issue intermittently even after linking emulator to emulator-arm. The emulator processes keep piling up because the plugin does not kill them after unsuccessfully trying to connect to them. I have tried to fix the issue by building a private version of the plugin with setting the ignore variable to true even for UNIX but it did not help. My environment is Xen Linux 3.2.0-3-amd64 #1 SMP 86_64 Debian GNU/Linux wheezy/sid. One problem I have had is that the emulator does not always get the display started by the xvnc plugin right because you cannot specify the display that the xvnc plugin starts. Building remotely on madmax2 in workspace /var/lib/jenkins/projects/avt/tests Starting xvnc tests $ vncserver :11 -localhost -nolisten tcp New 'X' desktop is madmax2.ecolane.com:11 Starting applications specified in /var/lib/jenkins/.vnc/xstartup Log file is /var/lib/jenkins/.vnc/madmax2.ecolane.com:11.log android Using Android SDK: /opt/adt-bundle-linux-x86_64/sdk android Waiting 1 seconds before starting emulator... $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb start-server android Starting Android emulator $ /opt/adt-bundle-linux-x86_64/sdk/tools/emulator -no-boot-anim -ports 56341,34347 -avd Android2.2GoogleAPIs -no-snapshot-load -no-snapshot-save daemon not running. starting it now on port 50229 * daemon started successfully * android Emulator did not appear to start; giving up $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb disconnect localhost:34347 android Stopping Android emulator $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb kill-server Taking screenshot. tests $ import -window root -display :11 screenshot.jpg Terminating xvnc. $ vncserver -kill :11 Killing Xtightvnc process ID 18436 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
[JIRA] (JENKINS-14901) Emulator start failed on Ubuntu (SDK 20.0.3)
David Tanner commented on JENKINS-14901 Emulator start failed on Ubuntu (SDK 20.0.3) I also have this issue and was able to get the plugin to recognize the launched plugin by renaming emulator-arm to emulator 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
[JIRA] (JENKINS-14901) Emulator start failed on Ubuntu (SDK 20.0.3)
Kostiantyn Madiar commented on JENKINS-14901 Emulator start failed on Ubuntu (SDK 20.0.3) Same issue, this workaround helped,but in my case i know how to solve this problem without this workaround. I just installed xvnc plugin and check "Run Xvnc during build" in job and that helped. Maybe new emulator needs x session. Debian 6 x64, Jenkins ver. 1.466.2, SDK 20.0.3 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
