|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
Ok - I've replicated the issue. It happens when Xvfb's lock file is removed, but tge display is still running.
1. Start a display on Jenkins Slave: /usr/bin/Xvfb :1972 -screen 0 1024x768x24 &
2. Remove the corresponding locl file: rm -rf /tmp/.X1972-lock
3. Run a simply Jenkins job that starts Xvfb on display 1972, with a single build task (e.g. a
4. Run build job
Build job passes successfully, even though the Xvfb plugin logs an error.
Started by user Cross, Richard (Contractor)
[EnvInject] - Loading node environment variables.
Building remotely on appduvirtual0c9 in workspace /buildstore/jenkins_appduvirtual0c9_slave/workspace/Xvfb_test_failure_scenario
Xvfb starting$ /usr/bin/Xvfb :1972 -screen 0 1024x768x24 -fbdir /buildstore/jenkins_appduvirtual0c9_slave/2014-02-03_12-23-504926962666561200040xvfb
_XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't already running
unlink: No such file or directory
unlink failed, Invalid argument[Xvfb_test_failure_scenario] $ /bin/sh -xe /tmp/hudson7411154595497137988.sh
+ echo This should only run is Xvfb is successful.
This should only run is Xvfb is successful.
Xvfb stopping
Notifying upstream projects of job completion
Finished: SUCCESS