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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | ------- Additional Comments From [EMAIL PROTECTED] 2003-09-13 17:59 ------- I'm sorry, but I'm unable to reproduce your results with a freshly downloaded and built Ant 1.5.4 tree. I'm using JUnit 3.8.1 if that perhaps is the deciding factor. I've slightly modified your build.xml as shown below: <?xml version="1.0"?> <project name="test" default="all"> <target name="all"> <junit fork="yes" timeout="5000" haltOnFailure="true" printsummary="yes"> <classpath> <pathelement path="."/> </classpath> <test name="Test2" outfile="result"> <formatter type="xml"/> </test> </junit> </target> </project> And I get the following output: ~/opt/ant/bin/ant -version Apache Ant version 1.5.4 compiled on September 13 2003 ~/quux $~/opt/ant/bin/ant Buildfile: build.xml all: [junit] Running Test2 BUILD SUCCESSFUL Total time: 8 seconds If I remove the timeout on the same test (which simply has a 10 second delay in it), I get: ~/opt/ant/bin/ant Buildfile: build.xml all: [junit] Running Test2 [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 10.167 sec BUILD SUCCESSFUL Total time: 13 seconds --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
