Matti Linnanvuori edited a comment on Bug JENKINS-14901

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

Reply via email to