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/12/04 16:41:23 UTC

DO NOT REPLY [Bug 25205] New: - timeout on results in wrong timing information

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=25205>.
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=25205

timeout on <junit> results in wrong timing information

           Summary: timeout on <junit> results in wrong timing information
           Product: Ant
           Version: 1.6Beta
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Optional Tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: wander@xs4all.nl


A timeout during a <junit> with formatter="xml" results in the following xml file:

<?xml version="1.0" encoding="UTF-8" ?>
<testsuite errors="1" failures="0" name="org.example.FooTest" tests="1" time="0.0">
  <properties></properties>
  <testcase classname="org.apache.tools.ant.taskdefs.optional.junit.JUnitTask$1"
name="unknown" time="0.0050">
    <error message="Timeout occurred"
type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError:
Timeout occurred
</error>
  </testcase>
</testsuite>

Meaning that the total testcase took 0.0 sec to complete and the timed out
testmethod took 0.005 seconds to complete. (Which is what the HTML report states
after running <junit-report>)

This is neither consistent nor correct, it should be at least the value
specified in the timeout attribute of the <junit> task.

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