-
Sven Sandberg authored
@suite/innodb/t/innodb_bug60049.test - The error is expected after dropping mysql system table innodb_table_stats, so we can safely suppress it, because mysql.innodb_table_stats is dropped in the test. @mysql-test/suite/perfschema/r/threads_mysql.result - Display the compression thread info when gtid_mode is OFF, since MySQL server starts the compression thread even if gtid_mode is OFF in the wl7083. @mysql-test/suite/rpl/t/rpl_gtids_table_disable_log_slave_updates.test - Remove a possible race from the test (FLUSH LOGS may already have signalled complete_compression when the wait starts). Instead, simplify it to avoid using debug sync points when forcing a gtid_executed table compression.
Sven Sandberg authored@suite/innodb/t/innodb_bug60049.test - The error is expected after dropping mysql system table innodb_table_stats, so we can safely suppress it, because mysql.innodb_table_stats is dropped in the test. @mysql-test/suite/perfschema/r/threads_mysql.result - Display the compression thread info when gtid_mode is OFF, since MySQL server starts the compression thread even if gtid_mode is OFF in the wl7083. @mysql-test/suite/rpl/t/rpl_gtids_table_disable_log_slave_updates.test - Remove a possible race from the test (FLUSH LOGS may already have signalled complete_compression when the wait starts). Instead, simplify it to avoid using debug sync points when forcing a gtid_executed table compression.
Loading