maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Diesler (JIRA)" <j...@codehaus.org>
Subject [jira] (SUREFIRE-1014) Unparsable test report XML when sysout contains invalid XML
Date Fri, 12 Jul 2013 10:28:05 GMT
Thomas Diesler created SUREFIRE-1014:
----------------------------------------

             Summary: Unparsable test report XML when sysout contains invalid XML
                 Key: SUREFIRE-1014
                 URL: https://jira.codehaus.org/browse/SUREFIRE-1014
             Project: Maven Surefire
          Issue Type: Bug
          Components: Maven Surefire Plugin
    Affects Versions: 2.15
            Reporter: Thomas Diesler


Jenkins cannot generate test reports from this

{code}
  <testcase name="testDeferredBundleWithFailure" classname="org.jboss.test.osgi.example.jpa.PersistenceTestCase"
time="0">
    <skipped message="[AS7-5654] Cannot restart jpa bundle after activation failure"/>
    <system-out>&amp#;[0m04:25:37,808 INFO  [org.jboss.osgi.framework] (MSC service
thread 1-7) JBOSGI011003: Bundle stopped: startlevel-testcase:0.0.0
&amp#;[0m&amp#;[0m04:25:37,811 INFO  [org.jboss.osgi.framework] (MSC service thread
1-7) JBOSGI011005: Bundle uninstalled: startlevel-testcase:0.0.0
&amp#;[0m&amp#;[0m04:25:37,813 INFO  [org.jboss.as.server.deployment] (MSC service
thread 1-7) JBAS015877: Stopped deployment startlevel-testcase (runtime-name: startlevel-testcase)
in 5ms
&amp#;[0m&amp#;[0m04:25:37,947 INFO  [org.jboss.as.repository] (management-handler-thread
- 3) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/jbosgi-remote-wildfly/jbosgi/testsuite/example/target/wildfly-8.0.0.Alpha3-SNAPSHOT/standalone/data/content/05/a1644a3f4393604a469058be52a8ff22a7ddf9/content
&amp#;[0m&amp#;[0m04:25:37,947 INFO  [org.jboss.as.server] (management-handler-thread
- 3) JBAS018558: Undeployed "startlevel-testcase" (runtime-name: "startlevel-testcase")
&amp#;[0m&amp#;[0m04:25:37,947 INFO  [org.jboss.as.controller] (management-handler-thread
- 3) JBAS014774: Service status report
JBAS014776:    Newly corrected services:
      service jboss.module.service."deployment.osgi-startlevel-a".main (no longer required)

&amp#;[0m&amp#;[0m04:25:38,065 INFO  [org.jboss.as.repository] (management-handler-thread
- 4) JBAS014900: Content added at location /mnt/hudson_workspace/workspace/jbosgi-remote-wildfly/jbosgi/testsuite/example/target/wildfly-8.0.0.Alpha3-SNAPSHOT/standalone/data/content/98/b7aa8f04dae4a922300c8fe4b522d7ed231555/content
&amp#;[0m&amp#;[0m04:25:38,066 INFO  [org.jboss.as.server.deployment] (MSC service
thread 1-3) JBAS015876: Starting deployment of "osgi-jpa-test" (runtime-name: "osgi-jpa-test")
&amp#;[0m&amp#;[0m04:25:38,078 INFO  [org.jboss.osgi.framework] (MSC service thread
1-1) JBOSGI011001: Bundle installed: osgi-jpa-test:0.0.0
&amp#;[0m&amp#;[0m04:25:38,090 INFO  [org.jboss.as.arquillian] (MSC service thread
1-3) Arquillian deployment detected: ArquillianConfig[service=jboss.arquillian.config.osgi-jpa-test,unit=osgi-jpa-test,tests=[org.jboss.test.osgi.example.jpa.PersistenceTestCase]]
&amp#;[0m&amp#;[0m04:25:38,093 INFO  [org.jboss.osgi.framework] (MSC service thread
1-3) JBOSGI011002: Bundle started: osgi-jpa-test:0.0.0
&amp#;[0m&amp#;[0m04:25:38,226 INFO  [org.jboss.as.server] (management-handler-thread
- 4) JBAS018559: Deployed "osgi-jpa-test" (runtime-name : "osgi-jpa-test")
&amp#;[0m</system-out>
  </testcase>
{code}

we get 

{code}
Caused by: org.xml.sax.SAXParseException: The reference to entity "amp" must end with the
';' delimiter.
	at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
	at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
	at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
	at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1427)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEntityReference(XMLDocumentFragmentScannerImpl.java:1849)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3033)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647)
	at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
	at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
	at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
	at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
	at org.dom4j.io.SAXReader.read(SAXReader.java:465)
	... 18 more
Build step 'Publish JUnit test result report' changed build result to FAILURE
Notifying upstream projects of job completion
Finished: FAILURE
{code}

--
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

Mime
View raw message