From 00ddea4f2f7d20e09a28655b2f30a4c014e9344a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marko=20M=C3=A4kel=C3=A4?= Date: Tue, 27 Oct 2020 09:52:42 +0200 Subject: MDEV-24024 innodb.ibuf_not_empty failed in buildbot Probably due to the changes to page flushing in MDEV-23399 (commit 7cffb5f6e8a231a041152447be8980ce35d2c9b8) the command CHECK TABLE would occasionally report a different number of rows for the corrupted secondary index. (The reported number was 991 instead of 990 on one occasion.) Let us map all numbers to 990 in the output. We only care that the injected corruption will be detected. --- mysql-test/suite/innodb/t/ibuf_not_empty.test | 1 + 1 file changed, 1 insertion(+) diff --git a/mysql-test/suite/innodb/t/ibuf_not_empty.test b/mysql-test/suite/innodb/t/ibuf_not_empty.test index 3b254177497..545a78c887e 100644 --- a/mysql-test/suite/innodb/t/ibuf_not_empty.test +++ b/mysql-test/suite/innodb/t/ibuf_not_empty.test @@ -68,6 +68,7 @@ EOF --let $restart_parameters= --innodb-force-recovery=6 --innodb-change-buffer-dump --source include/start_mysqld.inc +--replace_regex /contains \d+ entries/contains 990 entries/ check table t1; --source include/shutdown_mysqld.inc -- cgit v1.2.1