diff options
| author | Bjorn Munch <bjorn.munch@oracle.com> | 2011-04-27 09:45:23 +0200 |
|---|---|---|
| committer | Bjorn Munch <bjorn.munch@oracle.com> | 2011-04-27 09:45:23 +0200 |
| commit | 005514b4877ffdf7ede1c5b5178b0b21d9a6db5d (patch) | |
| tree | e1a4aee4735fbcd5eebf51e80ffd053953119145 /mysql-test/mysql-test-run.pl | |
| parent | 810e02edf2b9f2b65842c0b5054d95a0f4136b0b (diff) | |
| download | mariadb-git-005514b4877ffdf7ede1c5b5178b0b21d9a6db5d.tar.gz | |
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
Diffstat (limited to 'mysql-test/mysql-test-run.pl')
| -rwxr-xr-x | mysql-test/mysql-test-run.pl | 1 |
1 files changed, 1 insertions, 0 deletions
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 |