|
||||||||
|
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/d/optout.
Thanks for your response and the references!
I configured the jenkins jobs which use the plugin to use the executor + offset 1 as display variable (this is the default anyways). So it can't be that there are other jobs using the same display number since the executor number is unique and two jobs can't use the same executor. We are using xvfb only for this purpose as well (i checked and xvfb is deactivated in existing jobs by default after the installation). I checked the .X*-lock files and the PID inside is no longer valid/used.
Could it be that the lock is being deleted to early (process still running?) What happens if the display is started but the jenkins fails? Is there another configuration that matters ("Shutdown Xvfb with whole job, not just with the main build action" is not set for my jobs as there is only one gradle call inside)
Thank you for your help and your work here, it is very much appreciated!