ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 7980] - JUnit spawned thread spits output to STDOUT, not formatter destination
Date Tue, 16 Apr 2002 15:31:28 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7980>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7980

JUnit spawned thread spits output to STDOUT, not formatter destination

bodewig@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|DUPLICATE                   |



------- Additional Comments From bodewig@apache.org  2002-04-16 15:31 -------
Actually this is not really a duplicate of bug 5377.

5377 was concerned with output in the fork="true" case, which work now - with
or without spawned threads.

This one is a lot more difficult to tackle (to be honest, I don't know how).
What we have here is that a test case spawns a thread in Ant's VM.  

Ant's output handling system doesn't know about the new thread and therefore
will not pass the output to the junit task but send it to the logging system
directly.  As the <junit> task doesn'r receive the output, it cannot
suppress/swallow it.

If we simply pass all output to junit (by replacing System.out directly),
junit will receive the output of different tasks when running inside <parallel>
as well and label it as test case output.  Bad.

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message