When using the Xvfb plugin, if the plugin fails to establish a connection, then the build should fail, as any tests that depend on an Xvfb display are bound to fail also. Or, at least there should be an option in the advance settings to fail the job if Xvfb fails.

Currently, the plugin simply logs an error, and then proceeds with the rest of the build job.

12:28:14 Xvfb starting$ /usr/bin/Xvfb :1958 -screen 0 1024x768x24 -fbdir /buildstore/jenkins_0c9_slave/2014-01-29_12-28-139011048368266724308xvfb
12:28:14 _XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed
12:28:14 _XSERVTransMakeAllCOTSServerListeners: server already running
12:28:14
12:28:14 Fatal server error:
12:28:14 Cannot establish any listening sockets - Make sure an X server isn't already running
12:28:14 unlink: No such file or directory
12:28:14 unlink failed, Invalid argument
12:28:14 ERROR: Xvfb failed to start, consult the lines above for errors
12:28:29 ha:AAAAWB+LCAAAAAAAAABb85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWAAAAA=Copied 1 artifact from "ha:AAAAsB+LCAAAAAAAAABb85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyTVzHb1RttJBUeZGJg8GdhyUvPSSzJ8GJhLi3JKGIR8shLLEvVzEvPS9YNLijLz0q0rihik0IxzhtAgwxgggJGJgaGiAMjQLmEw0M/KT9L3TSwuSS2KL0lNzDUwjHcsLcnPTSxJTYl3K81LLsnMz0vMiQ9JLS4B2qAPABqeEK21AAA
....
....
.... [rest of build job proceeds, and inevitably fails]
....