You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2003/09/13 03:09:12 UTC
DO NOT REPLY [Bug 23150] New: -
JUnitTask does not mark timed out tests as failed when forked
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
Summary: JUnitTask does not mark timed out tests as failed when
forked
Product: Ant
Version: 1.5.4
Platform: PC
OS/Version: Linux
Status: NEW
Severity: Normal
Priority: Other
Component: Optional Tasks
AssignedTo: dev@ant.apache.org
ReportedBy: daveg@permabit.com
JUnitTask now reports that tasks that have timed out by adding an error
to the JUnitResultFormatter (in logTimeout()), but the test itself is
not marked as having failed, since the retVal is not marked as failed
in executeAsForked().
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org