summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEugene Kosov <claprix@yandex.ru>2019-12-04 22:29:33 +0700
committerEugene Kosov <claprix@yandex.ru>2019-12-05 23:09:57 +0700
commit42bad56aab25db4a05c676ba99290949ad4e1c34 (patch)
treee5cb43d156d1e9fe468bd2fe4484e5cb1fa843c8
parent2b7e461cc06ea5ca167e16ff643f0b597aba118d (diff)
downloadmariadb-git-42bad56aab25db4a05c676ba99290949ad4e1c34.tar.gz
MDEV-21014 MTR does not detect {A,M,T,L,UB}SAN errors which happen upon server shutdown
Let MTR check for error existence after running a test and return it back to user. Error reporting itset might be much better, but first of all we need to see that something went wrong.
-rwxr-xr-xmysql-test/mysql-test-run.pl2
1 files changed, 2 insertions, 0 deletions
diff --git a/mysql-test/mysql-test-run.pl b/mysql-test/mysql-test-run.pl
index a44dbe92a3d..77c307727a6 100755
--- a/mysql-test/mysql-test-run.pl
+++ b/mysql-test/mysql-test-run.pl
@@ -4401,6 +4401,8 @@ sub extract_warning_lines ($$) {
qr/missing DBUG_RETURN/,
qr/Attempting backtrace/,
qr/Assertion .* failed/,
+ qr/Sanitizer/,
+ qr/runtime error:/,
);
# These are taken from the include/mtr_warnings.sql global suppression
# list. They occur delayed, so they can be parsed during shutdown rather