Re: Count mauve results better

[Anthony Green <green@cygnus.com>]

Warren wrote:
> You'll also want to make this mod to the 'test_mauve' proc (otherwise
> you'll only see a difference when running the tests using a simulator).

Thanks - you're absolutely right.  And my ChangeLog entry was
misleading.  This patch replaces the previous one.  It's in the
trunk and the branch.

        * libjava.mauve/mauve.exp: Don't stop counting test results
        prematurely.

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 23:27:24
@@ -152,10 +152,6 @@ proc test_mauve {} {
 
     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
@@ -315,10 +311,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