Skip to content

Commit

Permalink
MDEV-10887: innodb.innodb_stats_fetch_nonexistent fails in buildbot o…
Browse files Browse the repository at this point in the history
…n Windows

Problem was that test innodb.innodb_stats_fetch_corrupted will post
a error InnoDB: Error: Table "mysql"."innodb_index_stats" not found
to a error log and test ignores that message. However, following tests
might see this error also and they might not ignore this error.
Force a server restart after innodb.innodb_stats_fetch_corrupted
to get clean log.
  • Loading branch information
Jan Lindström committed Sep 27, 2016
1 parent 452e849 commit 661d08c
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions mysql-test/suite/innodb/t/innodb_stats_fetch_corrupted.test
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,8 @@
# functionality tested here is not related to the page size, so we only
# test with 16k page size.
-- source include/have_innodb_16k.inc
# server restart
-- source include/not_embedded.inc

call mtr.add_suppression("InnoDB: Error: Table \"mysql\".\"innodb_index_stats\" not found");
call mtr.add_suppression("InnoDB: Error: Fetch of persistent statistics requested for table");
Expand Down Expand Up @@ -43,3 +45,6 @@ FROM information_schema.tables WHERE table_name = 'test_ps_fetch_corrupted';
ALTER TABLE mysql.innodb_index_stats_ RENAME TO mysql.innodb_index_stats;

DROP TABLE test_ps_fetch_corrupted;

# force server restart to clean up log from above error
--source include/restart_mysqld.inc

0 comments on commit 661d08c

Please sign in to comment.