From 005514b4877ffdf7ede1c5b5178b0b21d9a6db5d Mon Sep 17 00:00:00 2001
From: Bjorn Munch <bjorn.munch@oracle.com>
Date: Wed, 27 Apr 2011 09:45:23 +0200
Subject: [PATCH] Bug #12373916 MTR SHOULD FLAG PRESENCE OF VALGRIND MEMORY
 LEAK REPORTS IN A CLEARER WAY Fix: it only worked if some worker had valgrind
 report from its last test Flag has to be set both places where report is
 printed

---
 mysql-test/mysql-test-run.pl | 1 +
 1 file changed, 1 insertion(+)

diff --git a/mysql-test/mysql-test-run.pl b/mysql-test/mysql-test-run.pl
index da07d49c24f..c288a16d233 100755
--- a/mysql-test/mysql-test-run.pl
+++ b/mysql-test/mysql-test-run.pl
@@ -5677,6 +5677,7 @@ sub valgrind_exit_reports() {
                         @culprits);
             mtr_print_line();
             print ("$valgrind_rep\n");
+            $found_err= 1;
             $err_in_report= 0;
           }
           # Make ready to collect new report