Gareth Curtis created JENKINS-13961:
---------------------------------------

             Summary: Fitnesse exception loading resource testResults.vm if job 
name contains a comma (,)
                 Key: JENKINS-13961
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13961
             Project: Jenkins
          Issue Type: Bug
          Components: fitnesse
    Affects Versions: current
         Environment: tested on Windows 7 32 bit and Windows Server 2008 R2 64 
bit
            Reporter: Gareth Curtis
            Priority: Trivial


If the name of a job (and therefore also the workspace folder) includes a 
comma, an exception occurs (when the FitNesse plugin attempts to read the test 
results?)

Workaround is easy - just rename the job. But thought it best to document the 
issue, it may save someone else some time.

A copy from console output below:
------------

FitNesse (v20111026) Started...
        port:              8081
        root page:         fitnesse.wiki.FileSystemPage at C:\Program 
Files\Jenkins\jobs\Run engage.installer, - from nightly build 
folder\workspace/FitNesseRoot
        logger:            none
        authenticator:     fitnesse.authentication.PromiscuousAuthenticator
        html page factory: fitnesse.html.HtmlPageFactory
        page version expiration set to 14 days.

Connnecting to 
http://localhost:8081/EngageAcceptanceTests.AuthenticationWithLoginTests?test&format=xml&includehtml
Connected: 200/OK
Xml results saved as windows-1252 to C:\Program Files\Jenkins\jobs\Run 
engage.installer, - from nightly build folder\workspace\fitnesseResults.xml
org.apache.velocity.exception.ResourceNotFoundException: Unable to find 
resource 'testResults.vm'
        at 
org.apache.velocity.runtime.resource.ResourceManagerImpl.loadResource(ResourceManagerImpl.java:483)
        at 
org.apache.velocity.runtime.resource.ResourceManagerImpl.getResource(ResourceManagerImpl.java:354)
        at 
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1400)
        at 
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1380)
        at 
org.apache.velocity.app.VelocityEngine.getTemplate(VelocityEngine.java:401)
        at 
fitnesse.responders.run.formatters.XmlFormatter.writeResults(XmlFormatter.java:132)
        at 
fitnesse.responders.run.formatters.XmlFormatter.writeResults(XmlFormatter.java:117)
        at 
fitnesse.responders.run.formatters.PageHistoryFormatter.testComplete(PageHistoryFormatter.java:27)
        at 
fitnesse.responders.run.formatters.CompositeFormatter.testComplete(CompositeFormatter.java:65)
        at 
fitnesse.responders.run.MultipleTestsRunner.testComplete(MultipleTestsRunner.java:238)
        at fitnesse.responders.run.TestSystem.testComplete(TestSystem.java:116)
        at 
fitnesse.responders.run.slimResponder.SlimTestSystem.runTestsAndGenerateHtml(SlimTestSystem.java:228)
        at 
fitnesse.responders.run.MultipleTestsRunner.executeTestSystemPages(MultipleTestsRunner.java:140)
        at 
fitnesse.responders.run.MultipleTestsRunner.startTestSystemAndExecutePages(MultipleTestsRunner.java:120)
        at 
fitnesse.responders.run.MultipleTestsRunner.executePagesInTestSystem(MultipleTestsRunner.java:106)
        at 
fitnesse.responders.run.MultipleTestsRunner.internalExecuteTestPages(MultipleTestsRunner.java:86)
        at 
fitnesse.responders.run.MultipleTestsRunner.executeTestPages(MultipleTestsRunner.java:58)
        at 
fitnesse.responders.run.TestResponder.performExecution(TestResponder.java:145)
        at 
fitnesse.responders.run.TestResponder.doSending(TestResponder.java:45)
        at 
fitnesse.responders.ChunkingResponder.startSending(ChunkingResponder.java:67)
        at 
fitnesse.responders.ChunkingResponder.access$000(ChunkingResponder.java:17)
        at 
fitnesse.responders.ChunkingResponder$RespondingRunnable.run(ChunkingResponder.java:106)
        at java.lang.Thread.run(Unknown Source)

31.05.2012 11:40:24 org.apache.velocity.runtime.log.JdkLogChute log
SCHWERWIEGEND: ResourceManager : unable to find resource 'testResults.vm' in 
any resource loader.
31.05.2012 11:40:24 org.apache.velocity.runtime.log.JdkLogChute log
SCHWERWIEGEND: ResourceManager : unable to find resource 'testResults.vm' in 
any resource loader.
org.apache.velocity.exception.ResourceNotFoundException: Unable to find 
resource 'testResults.vm'
        at 
org.apache.velocity.runtime.resource.ResourceManagerImpl.loadResource(ResourceManagerImpl.java:483)
        at 
org.apache.velocity.runtime.resource.ResourceManagerImpl.getResource(ResourceManagerImpl.java:354)
        at 
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1400)
        at 
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1380)
        at 
org.apache.velocity.app.VelocityEngine.getTemplate(VelocityEngine.java:401)
        at 
fitnesse.responders.run.formatters.XmlFormatter.writeResults(XmlFormatter.java:132)
        at 
fitnesse.responders.run.formatters.XmlFormatter.writeResults(XmlFormatter.java:117)
        at 
fitnesse.responders.run.formatters.XmlFormatter.allTestingComplete(XmlFormatter.java:109)
        at 
fitnesse.responders.run.formatters.BaseFormatter.errorOccured(BaseFormatter.java:38)
        at 
fitnesse.responders.run.formatters.CompositeFormatter.errorOccured(CompositeFormatter.java:28)
        at 
fitnesse.responders.run.MultipleTestsRunner.exceptionOccurred(MultipleTestsRunner.java:243)
        at 
fitnesse.responders.run.MultipleTestsRunner.executeTestPages(MultipleTestsRunner.java:64)
        at 
fitnesse.responders.run.TestResponder.performExecution(TestResponder.java:145)
        at 
fitnesse.responders.run.TestResponder.doSending(TestResponder.java:45)
        at 
fitnesse.responders.ChunkingResponder.startSending(ChunkingResponder.java:67)
        at 
fitnesse.responders.ChunkingResponder.access$000(ChunkingResponder.java:17)
        at 
fitnesse.responders.ChunkingResponder$RespondingRunnable.run(ChunkingResponder.java:106)
        at java.lang.Thread.run(Unknown Source)


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to