summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarko Mäkelä <marko.makela@mariadb.com>2020-11-20 08:06:24 +0200
committerMarko Mäkelä <marko.makela@mariadb.com>2020-11-20 08:06:24 +0200
commit3c8ecb5bbd642a7a53fd2ad5e68f2be7d27ed8b1 (patch)
treeb48110fcc4ca26d7fe0c8a0321a78cf3db3854a5
parent8ac19be8a249f5592deac1f05cd099ddde603589 (diff)
downloadmariadb-git-3c8ecb5bbd642a7a53fd2ad5e68f2be7d27ed8b1.tar.gz
Run innodb_wl6326_big only in debug builds
The test seems to deterministically fail on RelWithDebInfo builds due to a timeout in wait_condition.inc. According to Matthias Leich (the original author of the test), the failure rate would reduce if we disabled the purge of transaction history by setting innodb_force_recovery=2. For now, let us run this stress test on debug builds only.
-rw-r--r--mysql-test/suite/innodb/t/innodb_wl6326_big.test4
1 files changed, 4 insertions, 0 deletions
diff --git a/mysql-test/suite/innodb/t/innodb_wl6326_big.test b/mysql-test/suite/innodb/t/innodb_wl6326_big.test
index 43de46b4125..27d02591b84 100644
--- a/mysql-test/suite/innodb/t/innodb_wl6326_big.test
+++ b/mysql-test/suite/innodb/t/innodb_wl6326_big.test
@@ -29,6 +29,10 @@
# vardir on tmpfs : ~ 375
# vardir on disk : ~ 546
--source include/big_test.inc
+# Possibly related to MDEV-16678, the test seems to deterministically fail on
+# non-debug builds. innodb_force_recovery=2 (disabling the purge of history)
+# would seem to help a little.
+--source include/have_debug.inc
# We go with "--send" and "--reap" and that fails with the embedded server.
--source include/not_embedded.inc
# Its intentional to not take the risk that a run with valgrind times out.