That says you need to install the Xfvb program on your Linux system.
Installing a package depends on the Linux variant, since there are several
different package managers.

Refer to
http://serverfault.com/questions/344793/install-xvfb-via-yum-yum-repository-for-xvfb
if
you're using Red Hat or CentOS.

Refer to your specific operating system for package management for it.

Mark Waite

On Tue, Nov 24, 2015 at 5:30 AM dhrumil shah <[email protected]>
wrote:

> First of all thanks for your reply.
>
> yes here I am runnig my tests on Linux. and as per you say i have
> installed xvfb plugin but still got below error:
> Here I have attached screen shot of XVfb configuration.
>
> Total time: 47 seconds
> ERROR: Failed to parse POMsjava.io.IOException 
> <http://stacktrace.jenkins-ci.org/search?query=java.io.IOException>: Cannot 
> run program "Xvfb": error=2, No such file or directory
>       at java.lang.ProcessBuilder.start(ProcessBuilder.java:1047) 
> <http://stacktrace.jenkins-ci.org/search/?query=java.lang.ProcessBuilder.start&entity=method>
>       at hudson.Proc$LocalProc.<init>(Proc.java:244) 
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.Proc$LocalProc.%3Cinit%3E&entity=method>
>       at hudson.Proc$LocalProc.<init>(Proc.java:216) 
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.Proc$LocalProc.%3Cinit%3E&entity=method>
>       at hudson.Launcher$LocalLauncher.launch(Launcher.java:816) 
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.Launcher$LocalLauncher.launch&entity=method>
>       at hudson.Launcher$ProcStarter.start(Launcher.java:382) 
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.Launcher$ProcStarter.start&entity=method>
>       at 
> org.jenkinsci.plugins.xvfb.XvfbBuildWrapper.launchXvfb(XvfbBuildWrapper.java:557)
>  
> <http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.xvfb.XvfbBuildWrapper.launchXvfb&entity=method>
>       at 
> org.jenkinsci.plugins.xvfb.XvfbBuildWrapper.setUp(XvfbBuildWrapper.java:622) 
> <http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.xvfb.XvfbBuildWrapper.setUp&entity=method>
>       at 
> hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:653)
>  
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun&entity=method>
>       at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) 
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.run&entity=method>
>       at hudson.model.Run.execute(Run.java:1741) 
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.execute&entity=method>
>       at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) 
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild.run&entity=method>
>       at hudson.model.ResourceController.execute(ResourceController.java:98) 
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.execute&entity=method>
>       at hudson.model.Executor.run(Executor.java:381) 
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.run&entity=method>
> Caused by: java.io.IOException 
> <http://stacktrace.jenkins-ci.org/search?query=java.io.IOException>: error=2, 
> No such file or directory
>       at java.lang.UNIXProcess.forkAndExec(Native Method)
>       at java.lang.UNIXProcess.<init>(UNIXProcess.java:186)
>       at java.lang.ProcessImpl.start(ProcessImpl.java:130)
>       at java.lang.ProcessBuilder.start(ProcessBuilder.java:1028)
>       ... 12 more
> Finished: FAILURE
>
>
>
>
>
>
>
> On Tuesday, November 24, 2015 at 5:17:42 PM UTC+5:30, Mark Waite wrote:
>
>> I think you may be trying to run your tests on a Unix variant (Linux,
>> FreeBSD, Solaris, etc.) but don't have an X Windows server to which the
>> firefox program can connect for displaying itself.
>>
>> If that's the case, then you should investigate either the Xvnc plugin or
>> the Xvfb plugin.  They both provide simple ways for Jenkins to start and
>> stop an X Windows server which can be used by tests running as part of the
>> job.
>>
>> If you're running on Windows, then the Jenkins slave needs to be allowed
>> to interact with the desktop.  You can either do that the simple way by
>> running the Jenkins slave from the desktop, or you if you must run your
>> Jenkins slave as a service, then you need to grant your service access to
>> the desktop.
>>
>> Mark Waite
>>
>> On Tue, Nov 24, 2015 at 4:40 AM dhrumil shah <[email protected]>
>> wrote:
>>
> Hello,
>>>
>>> When I run my Selenium Webdriver Simple Login script on jenkins through
>>> Git then it always skip my test cases and give me the below error.
>>>
>>> org.openqa.selenium.firefox.NotConnectedException: Unable to connect to
>>> host 127.0.0.1 on port 7055 after 45000 ms. Firefox console output:
>>>    [testng] No protocol specified
>>>    [testng] No protocol specified
>>>    [testng] Error: cannot open display: :0
>>>    [testng] No protocol specified
>>>    [testng] No protocol specified
>>>    [testng] Error: cannot open display: :0
>>>    [testng]
>>>    [testng]     at
>>> org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:118)
>>>    [testng]     at
>>> org.openqa.selenium.firefox.FirefoxDriver.startClient(FirefoxDriver.java:246)
>>>    [testng]     at
>>> org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:114)
>>>    [testng]     at
>>> org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:193)
>>>    [testng]     at
>>> org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:186)
>>>    [testng]     at
>>> org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:182)
>>>    [testng]     at
>>> org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:95)
>>>    [testng]     at Test.TestA.setUpTest(Unknown Source)
>>>    [testng]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>> Method)
>>>    [testng]     at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>    [testng]     at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>    [testng]     at java.lang.reflect.Method.invoke(Method.java:606)
>>>    [testng]     at
>>> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
>>>    [testng]     at
>>> org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564)
>>>    [testng]     at
>>> org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213)
>>>    [testng]     at
>>> org.testng.internal.Invoker.invokeConfigurations(Invoker.java:138)
>>>    [testng]     at org.testng.TestRunner.beforeRun(TestRunner.java:641)
>>>    [testng]     at org.testng.TestRunner.run(TestRunner.java:609)
>>>    [testng]     at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
>>>    [testng]     at
>>> org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
>>>    [testng]     at
>>> org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
>>>    [testng]     at org.testng.SuiteRunner.run(SuiteRunner.java:240)
>>>    [testng]     at
>>> org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
>>>    [testng]     at
>>> org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
>>>    [testng]     at
>>> org.testng.TestNG.runSuitesSequentially(TestNG.java:1224)
>>>    [testng]     at org.testng.TestNG.runSuitesLocally(TestNG.java:1149)
>>>    [testng]     at org.testng.TestNG.run(TestNG.java:1057)
>>>    [testng]     at org.testng.TestNG.privateMain(TestNG.java:1364)
>>>    [testng]     at org.testng.TestNG.main(TestNG.java:1333)
>>>    [testng]
>>>    [testng] ===============================================
>>>    [testng] Sample Test Suite
>>>    [testng] Total tests run: 1, Failures: 0, Skips: 1
>>>    [testng] Configuration Failures: 1, Skips: 1
>>>    [testng] ===============================================
>>>    [testng]
>>>    [testng] The tests failed.
>>>
>>>
>>>
>>> I have Searched a lot on Internet and some one told that upgrade the
>>> version of firefox and upgrade your jar file. But after upgrade my firefox
>>> version(42..0) and also the jar file (selenium-2.48.jar). but still get the
>>> same issue.
>>>
>>> After that I Connect through the putty and run the command 'firefox&'
>>> but it gives error like 'can not open display' and also tried with x11
>>> forward but it doesn't work.
>>>
>>> Any Help would be appreciated.
>>> Thanks
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>>
>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to [email protected].
>>
>>
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/c675d5d2-38bd-4d03-ae40-3d0534050e3d%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/c675d5d2-38bd-4d03-ae40-3d0534050e3d%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/5f99b53e-55b0-4849-abb3-9bbb205a6b5c%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/5f99b53e-55b0-4849-abb3-9bbb205a6b5c%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGZDHu%2BDxF40Z_Y%2BLpMAmOMEVo1nVtD%3DifRAp5WYnDFqg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to