|
||||||||
|
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-14483) Remaining Xvfb proce... [email protected] (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... [email protected] (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... [email protected] (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... [email protected] (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... [email protected] (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... [email protected] (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... [email protected] (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... [email protected] (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... [email protected] (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... [email protected] (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... [email protected] (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... [email protected] (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... [email protected] (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... [email protected] (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... [email protected] (JIRA)

Hi Zoran,
I justed tested the new version with following observations (according to console log) on Jenkins 1.434:
The result is that the first configuration works fine and properly stops the Xvfb process. But then there's no available X server for the following configuration jobs and so they fail (message: webkit_server: cannot connect to X server :16; F-webkit_server: cannot connect to X server :16).
I've only tested on a standalone Jenkins server but I think that this behaviour will fail especially in master-slave setups: if Xvfb is started on the master and the configuration jobs run on a slave every job will fail.
Sorry for the bad news![]()
Cheers,
Thorsten