Marko Mäkelä 56c60b2fc5 MDEV-16111 encryption.innodb_lotoftables failed in buildbot with wrong result ... Remove the test, because it easily fails with a result difference. Analysis by Thirunarayanan Balathandayuthapani: By default, innodb_encrypt_tables=0. 1) Test case creates 100 tables in innodb_encrypt_1. 2) creates another 100 unencrypted tables (encryption=off) in innodb_encrypt_2 3) creates another 100 encrypted tables (encryption=on) in innodb_encrypt_3 4) enabling innodb_encrypt_tables=1 and checking that only 100 encrypted tables exist. (already we have 100 in dictionary) 5) opening all tables again (no idea why) 6) After that, set innodb_encrypt_tables=0 and wait for 100 tables to be decrypted (already we have 100 unencrypted tables) 7) dropping all databases Sporadic failure happens because after step 4, it could encrypt the normal table too, because innodb_encryption_threads=4. This test was added in MDEV-9931, which was about InnoDB startup being slow due to all .ibd files being opened. There have been a number of later fixes to this problem. Currently the latest one is commit cad56fbaba, in which some tests (in particular the test innodb.alter_kill) could fail if all InnoDB .ibd files are read during startup. That could make this test redundant. Let us remove the test, because it is big, slow, unreliable, and does not seem to reliably catch the problem that all files are being read on InnoDB startup.		2019-06-12 19:08:49 +03:00
..
include	MDEV-9099: Test encryption.innodb_encryption_discard_import fails on buildbot	2016-10-29 10:09:06 +03:00
r	MDEV-16111 encryption.innodb_lotoftables failed in buildbot with wrong result	2019-06-12 19:08:49 +03:00
t	MDEV-16111 encryption.innodb_lotoftables failed in buildbot with wrong result	2019-06-12 19:08:49 +03:00
disabled.def	MDEV-14814: encryption.innodb_encryption-page-compression failed in buildbot with timeout on wait condition	2018-02-19 08:06:32 +02:00
suite.pm	move encryption tests to a dedicate suite	2015-05-13 14:27:16 +02:00