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 41104] - FileNotFoundException on forked batched junit tasks
Date Thu, 07 Dec 2006 00:24:35 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41104>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=41104





------- Additional Comments From peterreilly@apache.org  2006-12-06 16:24 -------
I have done some more testing with this.
If the classpath given to junit contains
ant.1.6 classes, one gets the FileNotFoundException.
and after this there should be a "Tests FAILED (crashed)"
- can you confirm that.

As regards the "false positive" summary report:
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 3.015 sec

I recompiled ant 1.6.5 and changed the summary output string to
reflect the version, I found that that this output comes from
the ant 1.6.5 summary report.

task:
    <junit printsummary="yes" fork="yes" forkmode="once">
      <classpath>
        <path path="build/classes"/>
        <fileset dir="lib" includes="*.jar"/>
        <fileset dir="l:/src/apache-ant-1.6.5/dist/lib" includes="*.jar"/>
      </classpath>
      <batchtest todir="build/reports">
        <fileset dir="src"/>  <!-- contains two test classes each of which have
                                   two tests -->
      </batchtest>
      <formatter type="xml"/>
    </junit>

I get the following output (after removing the spurious filenotfound exception):

Tests run: 2, Failures(1.6): 0, Errors: 0, Time elapsed: 0.328 sec
Tests run: 2, Failures(1.6): 0, Errors: 0, Time elapsed: 0.016 sec
Running Example
Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
Tests FAILED (crashed)

BUILD SUCCESSFUL

So it looks like the tests ran successfully,
the SummaryReport from ant 1.6 got used to report the success,
this is hidden from ant 1.7, which sees that the
junitrunner task seems to have crashed (1.7 has a new
handshake mechanism based on the error return and the
crash file) it reports this via the 1.7 summary report,
and then reports a crash.

Of course mixing ant1.6 and ant1.7 jars in the classpath
will not be good, the question is how can ant detect
this and report this to the user.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message