![]() |
|
|
|
|
Change By:
|
David T
(13/Apr/14 10:32 PM)
|
|
Description:
|
The http timeout for the FitNesse plugin seems to be ignored in the latest releases.
I am using the following versions
* Jenkins: 1.558
* Jre: 1.8.0-b132
* FitNesse plugin: 1.9 (using Java 1.7)
* FitNesse version: 20140201
I have configured the http timeout in the plugin to be 60000ms, however I get the error below
{code}
hudson.plugins.fitnesse.FitnesseBuilder: {fitnessePathToRoot=c:\Build\jobs\FitNesse-Tests\workspace\qa\fitNesse\FitNesseRoot, additionalFitnesseOptions=-e 0, fitnesseTestTimeout=60000, fitnesseJdk=Java7, fitnesseStart=True, fitnesseHttpTimeout=60000, fitnesseTargetIsSuite=false, fitnesseJavaOpts=-showversion -DTEST_RUNNER=dotNet\Runner.exe -Denv=QAB -Dbrowser=ph -Dtestdomain=import -Dlog=debug, fitnessePathToJar=c:\Build\jobs\FitNesse-Tests\workspace\qa\fitNesse\fitnesse-standalone.jar, fitnesseTargetPage=StandaLoneScripts.ChangeDatabaseToBulkStaffImport, fitnessePathToXmlResultsOut=c:\Build\jobs\FitNesse-Tests\workspace\fitnesse-updateDb-results.xml, fitnessePortLocal=8085, fitnesseJavaWorkingDirectory=c:\Build\jobs\FitNesse-Tests\workspace\qa\fitNesse\}
Starting new Fitnesse instance...
[fitNesse] $ C:\Java\jdk1.7.0_51\bin\java -showversion -DTEST_RUNNER=dotNet\Runner.exe -Denv=QAB -Dbrowser=ph -Dtestdomain=import -Dlog=debug -jar c:\Build\jobs\FitNesse-Tests\workspace\qa\fitNesse\fitnesse-standalone.jar -d c:\Build\jobs\FitNesse-Tests\workspace\qa\fitNesse -r FitNesseRoot -p 8085 -e 0
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)
root page: fitnesse.wiki.fs.FileSystemPage at c:\Build\jobs\FitNesse-Tests\workspace\qa\fitNesse/FitNesseRoot
logger: none
authenticator: fitnesse.authentication.PromiscuousAuthenticator
page factory: fitnesse.html.template.PageFactory
page theme: bootstrap
Starting FitNesse on port: 8085
Waited 30000ms for fitnesse to start.
Build step 'Execute fitnesse tests' marked build as failure
{code}
Note the fitnesseHttpTimeout=60000, however the job fails with "Waited 30000ms for fitnesse to start."
*NOTE*
As a workaround, if I turn on verbose logging for java
in the startup options of the plugin
, the FitNesse server starts as expected.
|
|
|
|
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
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
