|
||||||||
|
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.
Hi Jonathan,
thanks for reporting this, I would have probably never come across this. I've made a change in the way the plugin handles shutdown of Xvfb: it now detects the communication failure on shutdown, and keeps a list of Xvfb processes that need to be killed when the offending node comes back online. So when the node is back online the zombie Xvfb process will be (attempted to be) killed, and the temporary frame buffer directory will be deleted.
This does not help in case of master failure because the list is not persisted, but in that case you master fails I guess that you have greater problems than zombie Xvfb processes.
I've tested this by killing ssh connection between master and the slave, I would be very grateful if you could test it in your setup as well.
You'll need to use the experimental update site (http://updates.jenkins-ci.org/experimental/update-center.json) configured in the Advanced tab of the Plugin manager, the released version is 1.0.9-beta-2.
Zoran