t/TEST -deparse: always list unexpected passes

't/TEST -deparse' - which uses Porting/deparse-skips.txt to decide which
files are expected to fail when run after a round-trip through Deparse -
normally lists any expected-fail test files which unexpectedly
succeeded.

However, it only lists them if at least one other test file failed. Or
to put it another way, if all files expected to pass actually pass, it
doesn't mention that some expected to fail passed too.

This commit changes it so that it *always* lists such unexpected
successes.

Author: iabyn

t/TEST

@@ -918,16 +918,6 @@ EOT
 	    print "\t$test\n";
 	}
 
-	if (@unexpected_pass) {
-	    print <<EOF;
-
-The following scripts were expected to fail under -deparse (at least
-according to $deparse_skip_file), but unexpectedly succeeded:
-EOF
-	    print "\t$_\n" for sort @unexpected_pass;
-	    print "\n";
-	}
-
 	warn <<'SHRDLU_1';
 ### Since not all tests were successful, you may want to run some of
 ### them individually and examine any diagnostic messages they produce.
@@ -964,6 +954,17 @@ SHRDLU_5
 	    }
 	}
     }
+
+    if (@unexpected_pass) {
+	print <<EOF;
+
+The following scripts were expected to fail under -deparse (at least
+according to $deparse_skip_file), but unexpectedly succeeded:
+EOF
+	print "\t$_\n" for sort @unexpected_pass;
+	print "\n";
+    }
+
     printf "Elapsed: %d sec\n", time() - $t0;
     my ($user,$sys,$cuser,$csys) = times;
     my $tot = sprintf("u=%.2f  s=%.2f  cu=%.2f  cs=%.2f  scripts=%d  tests=%d",
@@ -991,6 +992,7 @@ SHRDLU_5
 }
 exit ($::bad_files != 0);
 
+
 # Collect platform, config data that should allow comparing
 # performance data between different machines.  With enough data,
 # and/or clever statistical analysis, it should be possible to