common-build.xml:

                <!-- ANT-compatible XMLs for jenkins records etc. -->
                <junit4:report-ant-xml dir="@{junit.output.dir}"
outputStreams="no" />

Like I said though -- I would *not* bring stdout/stderr back to those
XML files unless you want to deal with other problems resulting from
10+mb XML files. They also take a lot longer to serialize/ save than
just plain text output.

Dawid


On Tue, Mar 5, 2013 at 7:58 AM, Dawid Weiss
<[email protected]> wrote:
>> I though the XML report files contain the whole stdout?
>>
>> http://jenkins.thetaphi.de/job/Lucene-Solr-4.x-Linux/ws/solr/build/solr-core/test/TEST-org.apache.solr.update.TestAtomicUpdateErrorCases.xml
>>
>> But its empty... This would be the most "correct" variant. I know that by 
>> default stock JUnit saves the whole stdout/stderr in the XML file, but 
>> JUnit4 runner does not seem to do this?
>
> I used to emit stdout to those XML files but Solr emits so much
> logging information from certain tests that it got XML parsers/
> transformers hit OOM a few times on jenkins... I disabled it
> intentionally. Those plain-text files are still saved and they're more
> compact than XML output. I kept the XML output so that jenkins has
> stuff for its own analysis pipeline but standard output is not needed
> there.
>
> Dawid

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to