You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Zoltan Haindrich (Jira)" <ji...@apache.org> on 2020/10/09 12:40:00 UTC
[jira] [Created] (SUREFIRE-1852) ReporterException: When writing
xml report stdout/stderr
Zoltan Haindrich created SUREFIRE-1852:
------------------------------------------
Summary: ReporterException: When writing xml report stdout/stderr
Key: SUREFIRE-1852
URL: https://issues.apache.org/jira/browse/SUREFIRE-1852
Project: Maven Surefire
Issue Type: Bug
Affects Versions: 3.0.0-M4
Reporter: Zoltan Haindrich
I'm seeing some junit xml errors lately on ci.hive.apache.org (we are using 3.0.0-M4)
jenkins is unable to parse the junit result xml because its not a valid xml.
I was able to take a look at one of the problematic xmls and it doesn't "end well"
{code}
<system-err><![CDATA[
{code}
there is an exception in a dump file:
{code}
# Created at 2020-10-09T11:56:23.638
When writing xml report stdout/stderr
org.apache.maven.surefire.report.ReporterException: When writing xml report stdout/stderr
at org.apache.maven.plugin.surefire.report.StatelessXmlReporter.addOutputStreamElement(StatelessXmlReporter.java:508)
at org.apache.maven.plugin.surefire.report.StatelessXmlReporter.createOutErrElements(StatelessXmlReporter.java:484)
at org.apache.maven.plugin.surefire.report.StatelessXmlReporter.serializeTestClassWithoutRerun(StatelessXmlReporter.java:227)
at org.apache.maven.plugin.surefire.report.StatelessXmlReporter.serializeTestClass(StatelessXmlReporter.java:213)
at org.apache.maven.plugin.surefire.report.StatelessXmlReporter.testSetCompleted(StatelessXmlReporter.java:152)
at org.apache.maven.plugin.surefire.report.StatelessXmlReporter.testSetCompleted(StatelessXmlReporter.java:51)
at org.apache.maven.plugin.surefire.report.TestSetRunListener.testSetCompleted(TestSetRunListener.java:193)
at org.apache.maven.plugin.surefire.booterclient.output.ForkClient$TestSetCompletedListener.handle(ForkClient.java:166)
at org.apache.maven.plugin.surefire.booterclient.output.ForkClient$TestSetCompletedListener.handle(ForkClient.java:155)
at org.apache.maven.plugin.surefire.booterclient.output.ForkedChannelDecoder.handleEvent(ForkedChannelDecoder.java:275)
at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.processLine(ForkClient.java:409)
at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:379)
at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:88)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.FileNotFoundException: /tmp/stderr6375771388417760677deferred (No such file or directory)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.<init>(FileInputStream.java:138)
at org.apache.maven.surefire.shade.common.org.apache.commons.io.output.DeferredFileOutputStream.writeTo(DeferredFileOutputStream.java:321)
at org.apache.maven.plugin.surefire.report.Utf8RecodingDeferredFileOutputStream.writeTo(Utf8RecodingDeferredFileOutputStream.java:85)
at org.apache.maven.plugin.surefire.report.StatelessXmlReporter.addOutputStreamElement(StatelessXmlReporter.java:502)
... 13 more
{code}
I've found some very old 2-3 years old ticket (SUREFIRE-1239) which was fixed...it seems like a similar issue have resurfaced
--
This message was sent by Atlassian Jira
(v8.3.4#803005)