On Tue, 7 Feb 2012 20:43:58 -0500 Richard Lavoie <[email protected]> wrote:
> Ok I found the logs of the guy who successfully configured headless > jenkins with selenium. He used the svfb plugin and the envInject > plugin to set the DISPLAY environment variable. Well, what I've found so far is that the xvfb plugin just never works. And the DISPLAY variable is always set, so envInject shouldn't be needed -- but it still doesn't ever seem to work. But maybe something else is going on. . . . Found an init.d script to run Xvfb. Setting the DISPLAY variable in $JENKINS_HOME/.profile -- still doesn't work. That is, until it does. I've yet to find any rhyme nor reason for what makes it work, though at this point is seems like poking about in the shell as jenkins is the key, if it doesn't just start working on its own. So strange... So again. I restart jenkins. Xvfb is running via init script. DISPLAY is set in .profile in JENKINS_HOME. Build now... fails. Run a second time... success. Nothing is changed. What is going on? Repeat. Restart jenkins... using the init script, by the way, not the CLI jar. Build now... fails several times. Go to jenkins shell, hit enter. Now builds succeed?!? Nothing interesting in the logs. VM has only half a gig of ram, but that should be enough, no? So, once again, build now ... fails several times in a row. I go to the shell, hit "enter". Build now... succeeds. What on earth is happening, I wonder? Does anyone have suggestions for a possible avenue for nailing this down? [Last check, set up xvfb init to run in default runlevels, reboot. Now it works on first try. It's past time to move on to testing actual code, but I'm not terribly confident this won't just fall over at some point.] Cheers, -- Michael Higgins QA Intern, PuppetLabs [email protected]
