Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.0.38
-
None
Description
There are few tests that sporadically fail due to missed FLUSH TABLES
right before a crash (shutdown). BB shows few with a trace line the following:
rpl.rpl_mdev12179 'innodb,row' w2 [ fail ] Found warnings/errors in server log file! Test ended at 2018-01-25 22:06:19 line Attempting backtrace. You can use the following information to find out 2018-01-25 22:06:18 6 [ERROR] mysqld: Table './mysql/gtid_slave_pos' is marked as crashed and should be repaired
|
|
|
rpl.rpl_domain_id_filter_master_crash 'innodb,mix' w45 [ fail ] Found warnings/errors in server log file!
|
Test ended at 2019-03-25 11:30:18
|
line
|
2019-03-25 11:30:17 140138147560448 [ERROR] mysqld: Table './mysql/user' is marked as crashed and should be repaired
|
|
|
rpl.rpl_domain_id_filter_restart 'row' [ fail ] Test ended at 2017-12-05 15:17:59 CURRENT_TEST: rpl.rpl_domain_id_filter_restart --- /private/var/lib/buildslave/maria-slave/labrador/build/mysql-test/suite/rpl/r/rpl_domain_id_filter_restart.result 2017-12-04 02:52:56.000000000 +0200 +++ /private/var/lib/buildslave/maria-slave/labrador/build/mysql-test/suite/rpl/r/rpl_domain_id_filter_restart.reject 2017-12-05 15:17:59.000000000 +0200 @@ -39,6 +39,10 @@ SELECT * FROM t1; i 1 +Warnings: +Error 145 Table './test/t1' is marked as crashed and should be repaired +Error 1194 Table 't1' is marked as crashed and should be repaired
|
|
These tests, specifically ones for replication, need to be identified and refined.
A hint to locate: https://internal.askmonty.org/buildbot/reports/cross_reference#branch=&revision=&platform=&dt=&bbnum=&typ=&info=&fail_name=rpl&fail_variant=&fail_info_short=&fail_info_full=is+marked+as+crashed&limit=100