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] - [Patch] JUnitTask does not mark timed out tests as failed when forked
Date Wed, 17 Sep 2003 08:36:44 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

[Patch] JUnitTask does not mark timed out tests as failed when forked

bodewig@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From bodewig@apache.org  2003-09-17 08:36 -------
should be fixed with nightly build 2003-09-18.

I've taken a different approach than you Martijn, Ant will now explicitly mark
timed out tests as errors.

Your approach makes Execute#getExitCode match its documentation, but I think
we should better change the Javadocs instead.  There always is the additional
Execute#killedProcess and unconditionally returning 1 for a kille process would
make such a process look perfectly good on OpenVMS (where 1 means success - like
any other odd exit code).

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


Mime
View raw message