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 23150] - JUnitTask does not mark timed out tests as failed when forked
Date Mon, 15 Sep 2003 18:58:08 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=23150>.
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=23150

JUnitTask does not mark timed out tests as failed when forked





------- Additional Comments From ant@kruithof.xs4all.nl  2003-09-15 18:58 -------
While the Execute class claims that the Exit Value is set to 1 in case the
process is killed, it actually isn't. Especially when killed by the watchdog via
destroy the exit value may on certain java versions be set to 0 indicating
normal successful termination. 

The IBM JRE 1.4.1 on linux is known to show this behaviour. A patch is included
to set the exit value to 1 in case the watchdog kills the process as already
documented in getExitValue method of the Execute class. The exit value is also
set to one if the process is killed due to an InterruptedException.

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


Mime
View raw message