|
||||||||
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... zregv...@java.net (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... thorsten.kah...@dkd.de (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... zregv...@java.net (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... zregv...@java.net (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... thorsten.kah...@dkd.de (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... zregv...@java.net (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... zregv...@java.net (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... thorsten.kah...@dkd.de (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... zregv...@java.net (JIRA)
- [JIRA] (JENKINS-14483) Remaining Xvfb ... zregv...@java.net (JIRA)
Thorsten, thank you for testing!
I agree the best way would be to run Xvfb with each matrix job, that was my initial approach – but all matrix jobs share the same BuildWrapper instance, so process handle that is used for Xvfb termination/cleanup would be overwritten with each subsequent matrix job. I have to rethink my options here; I'll ask on jenkins-dev mailing list for starters – I must be missing something.
Anyways thank you for following this issue for so long and I hope to find the solution for it soon.