Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2(EOL)
-
None
-
10.2.4-2
Description
rpl.rpl_upgrade_master_info 'stmt' w3 [ fail ] Found warnings/errors in server log file!
|
Test ended at 2016-12-21 04:28:40
|
line
|
2016-12-21 4:28:23 1328198976 [ERROR] mysqld: Table './mysql/gtid_slave_pos' is marked as crashed and should be repaired
|
2016-12-21 4:28:23 1328198976 [Warning] Checking table: './mysql/gtid_slave_pos'
|
2016-12-21 4:28:23 1328198976 [ERROR] mysql.gtid_slave_pos: 1 client is using or hasn't closed the table properly
|
2016-12-21 4:28:24 1329714496 [ERROR] mysqld: Table './test/t1' is marked as crashed and should be repaired
|
2016-12-21 4:28:24 1329714496 [Warning] Checking table: './test/t1'
|
2016-12-21 4:28:24 1329714496 [ERROR] test.t1: 1 client is using or hasn't closed the table properly
|
^ Found warnings in /usr/local/mariadb-10.2.3-linux-x86_64/mysql-test/var/3/log/mysqld.2.err
|
ok
|
|
|
- skipping '/usr/local/mariadb-10.2.3-linux-x86_64/mysql-test/var/3/log/rpl.rpl_upgrade_master_info-stmt/'
|
|
|
Retrying test rpl.rpl_upgrade_master_info, attempt(2/3)...
|
Attachments
Issue Links
- relates to
-
MDEV-7069 Fix buildbot failures in main server trees
-
- Stalled
-
The issue above was probably that the build machine was overworked and the
shutdown took longer than 30 resp 10 seconds, which caused MyISAM tables
to be marked as crashed.
Fixed by flushing myisam tables before doing a forced shutdown/kill