hi! Hudson is great, thanks for writing it We're using it heavily
in the ASF these days: http://hudson.zones.apache.org/hudson/

Quick bug report. I'm writing a TAP-to-JUnit-XML conversion script for our
usage of Hudson in Apache SpamAssassin (which is written in perl, and therefore
uses TAP, the Test Anything Protocol, for test output interchange). the script
is here, if anyone's interested –
http://jmason.org/software/scripts/tap-to-junit-xml.txt

Anyway, there appears to be a small bug in how Hudson interprets the
single-file format (multiple <testsuite> blocks contained by one <testsuites>
container), compared to the multiple-file format (each file contains one
<testsuite> block, no <testsuites> container). With single-file format, the
<system-out> block is never displayed, whereas it is displayed fine with
multiple-file format.

I suspect the "it.parent" pointer in the jelly file is pointing at the
top-level parent node – the <testsuites> node – rather than the immediate
parent node, the <testsuite> node that the current <testcase> is contained by.
(that's just a guess, though.)

Here's single-file output:

http://hudson.zones.apache.org/hudson/job/SpamAssassin-tap-parser-test/36/testReport/make_test/t_basic_lint_t/test______1/

And here's what multi-file output looks like on the same input:

http://hudson.zones.apache.org/hudson/job/SpamAssassin-tap-parser-test/37/testReport/make_test/t_basic_lint_t/test______1/

if you need more info, let me know and I'll try to dig up a demo XML file.