Sorry, I feel like I'm beating a dead horse, but:
What I have found is, irrespective of *how* Xvfb is started, restarting Jenkins causes build with selenium to fail. So too fragile a configuration, this is. Is anyone on this list successfully using Xvfb and selenium plugin? I don't see it as an issue with either Jenkins or selenium plugin per se, but rather, how together they interact with the system. Ah. One more clue... I just, rather than 'restart', did stop, then start of Jenkins. Now the builds work again. So this may likely have something to do with the init script packaged with ubuntu? Just did it again, to be sure I'm seeing the same results with the same actions. Stop... start all is okay. Now, with 'restart'... yep, jobs fail. Stop... start and jobs get to use the framebuffer again. As for how Jenkins restarts itself, doing so causes the same failure. In theory, I should never have to restart Jenkins, but... theory often fails reality. Does anyone have a suggestion for another avenue to explore with some hope of being able to fix this? I don't think stopping and starting should be any different than restarting. But certainly, in this case, it is. :( Cheers, -- Michael Higgins QA Intern, PuppetLabs mhigg...@puppetlabs.com
