[MDEV-11621] rpl.rpl_gtid_stop_start fails sporadically in buildbot Created: 2016-12-21  Updated: 2018-05-22  Resolved: 2018-05-22

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.2
Fix Version/s: 10.2.10

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Michael Widenius
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-7069 Fix buildbot failures in main server ... Stalled
relates to MDEV-12731 rpl.rpl_gtid_stop_start fails with Va... Closed
Sprint: 10.2.4-2

 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-centos5-amd64/builds/4314/steps/test/logs/stdio

rpl.rpl_gtid_stop_start 'innodb,row'     w1 [ fail ]
        Test ended at 2016-12-21 04:28:24
 
CURRENT_TEST: rpl.rpl_gtid_stop_start
--- /usr/local/mariadb-10.2.3-linux-x86_64/mysql-test/suite/rpl/r/rpl_gtid_stop_start.result	2016-12-20 21:52:34.000000000 +0100
+++ /usr/local/mariadb-10.2.3-linux-x86_64/mysql-test/suite/rpl/r/rpl_gtid_stop_start.reject	2016-12-21 04:28:24.000000000 +0100
@@ -108,6 +108,10 @@
 5
 6
 7
+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
+Error	1034	1 client is using or hasn't closed the table properly
 *** MDEV-4486: Allow to start old-style replication even if mysql.gtid_slave_pos is unavailable
 connection server_2;
 include/stop_slave.inc
 
mysqltest: Result length mismatch



 Comments   
Comment by Michael Widenius [ 2016-12-21 ]

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

Comment by Michael Widenius [ 2018-05-22 ]

Fixed and pushed a long time ago

Generated at Thu Feb 08 07:51:23 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.