This is the mail archive of the
java-patches@sourceware.cygnus.com
mailing list for the Java project.
Count mauve results better
- To: java-patches@sourceware.cygnus.com
- Subject: Count mauve results better
- From: Anthony Green <green@cygnus.com>
- Date: Thu, 1 Jul 1999 15:32:36 -0700 (PDT)
Previously, the testing harness would only count a single failure in
any test in a testlet failed (and no passes). The harness should
ignore the return value from the test program.
I'm checking this into both the trunk and the 2.95 branch.
* libjava.mauve/mauve.exp: Don't stop counting test results just
because the harness returns non 0 value.
Index: libjava/testsuite/libjava.mauve/mauve.exp
===================================================================
RCS file: /cvs/java/libgcj/libjava/testsuite/libjava.mauve/mauve.exp,v
retrieving revision 1.3
diff -u -p -u -r1.3 mauve.exp
--- mauve.exp 1999/05/03 12:48:34 1.3
+++ mauve.exp 1999/07/01 22:29:00
@@ -315,10 +315,6 @@ proc test_mauve_sim {} {
set result [libjava_load [pwd]/DejaGNUTestHarness \
"$env(MAUVEDIR) $class" ""]
- if {[lindex $result 0] != "pass"} then {
- fail "Execute for $class"
- continue
- }
# Test for an exception thrown in the test harness itself. This
# isn't enough to test for all faults in the test harness, but
--
Anthony Green Cygnus Solutions
Sunnyvale, California