In response to Greg Roodt :
> Ah, good suggestion Stefan. That makes sense.
>
> I personally have had no issues capturing STDOUT, but I use the xml
> formatter to generate JUnit reports on Hudson. Also, this looks like a
> particularly nasty little problem if the test times out or runs out of sta
Ah, good suggestion Stefan. That makes sense.
I personally have had no issues capturing STDOUT, but I use the xml
formatter to generate JUnit reports on Hudson. Also, this looks like a
particularly nasty little problem if the test times out or runs out of stack
in a different environment.
Cheers
On 2010-03-05, Bill Moran wrote:
>
> timeout="1" maxmemory="512m" haltonfailure="no"
> tempdir="/tmp" failureProperty="test.failure">
> Unfortunately, this doesn't give me any output anywhere.
withOutAndErr should give you the output in most cases.
Since yo
In response to Greg Roodt :
> Ant normally captures stdout. Have you tried the xml formatter?
Not yet. If you have reason to believe that it will more accurately
report the output, my answer is that the other formatter should be
reported as broken. But I'll give it a go and see if I have more
s
Ant normally captures stdout. Have you tried the xml formatter?
It looks like your test is failing because its timing out, does it pass if
you remove the timeout?
Also, is there a reason you are using sysout rather than a logging framework
like log4J?
Cheers
Greg
On Fri, Mar 5, 2010 at 2:35 P
Hello all.
I'm fairly new to ant, we've been working with it a few weeks for our
Java excursions and most things are rolling along pretty well.
We've also been building a lot of tests using JUnit, and we're trying
to get them configured in ant so we can automatically run them nightly
on a dedica
