[MDEV-10688] rpl.rpl_row_log_innodb failed in buildbot Created: 2016-08-27  Updated: 2017-12-03  Resolved: 2017-12-03

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.1
Fix Version/s: 10.1.30

Type: Bug Priority: Minor
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

 Description   

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

rpl.rpl_row_log_innodb 'innodb_plugin,row' w3 [ fail ]
 
        Test ended at 2016-08-17 12:31:34
 
 
 
CURRENT_TEST: rpl.rpl_row_log_innodb
 
--- /usr/local/mariadb-10.1.17-linux-i686/mysql-test/suite/rpl/r/rpl_row_log_innodb.result	2016-08-17 12:02:31.000000000 +0200
 
+++ /usr/local/mariadb-10.1.17-linux-i686/mysql-test/suite/rpl/r/rpl_row_log_innodb.reject	2016-08-17 12:31:33.000000000 +0200
 
@@ -253,13 +253,13 @@
 
 slave-bin.000001	#	Rotate	#	#	slave-bin.000002;pos=POS
 
 include/show_binlog_events.inc
 
 Log_name	Pos	Event_type	Server_id	End_log_pos	Info
 
-slave-bin.000002	#	Binlog_checkpoint	#	#	slave-bin.000002
 
 slave-bin.000002	#	Gtid	#	#	GTID #-#-#
 
 slave-bin.000002	#	Query	#	#	use `test`; create table t2 (n int)ENGINE=InnoDB
 
 slave-bin.000002	#	Gtid	#	#	BEGIN GTID #-#-#
 
 slave-bin.000002	#	Table_map	#	#	table_id: # (test.t2)
 
 slave-bin.000002	#	Write_rows_v1	#	#	table_id: # flags: STMT_END_F
 
 slave-bin.000002	#	Xid	#	#	COMMIT /* XID */
 
+slave-bin.000002	#	Binlog_checkpoint	#	#	slave-bin.000002
 
 include/check_slave_is_running.inc
 
 show binlog events in 'slave-bin.000005' from 4;
 
 ERROR HY000: Error when executing command SHOW BINLOG EVENTS: Could not find target log
 
 
 
mysqltest: Result content mismatch



 Comments   
Comment by Alice Sherepa [ 2017-11-13 ]

now on 10.3 http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-centos5-amd64/builds/7368/steps/test/logs/stdio

CURRENT_TEST: rpl.rpl_row_log_innodb
 
--- /usr/local/mariadb-10.3.3-linux-x86_64/mysql-test/suite/rpl/r/rpl_row_log_innodb.result	2017-11-10 16:21:00.000000000 +0200
 
+++ /usr/local/mariadb-10.3.3-linux-x86_64/mysql-test/suite/rpl/r/rpl_row_log_innodb.reject	2017-11-10 19:09:18.225542730 +0200
 
@@ -268,7 +268,6 @@
 
 slave-bin.000001	#	Rotate	#	#	slave-bin.000002;pos=POS
 
 include/show_binlog_events.inc
 
 Log_name	Pos	Event_type	Server_id	End_log_pos	Info
 
-slave-bin.000002	#	Binlog_checkpoint	#	#	slave-bin.000002
 
 slave-bin.000002	#	Gtid	#	#	GTID #-#-#
 
 slave-bin.000002	#	Query	#	#	use `test`; create table t2 (n int)ENGINE=InnoDB
 
 slave-bin.000002	#	Gtid	#	#	BEGIN GTID #-#-#
 
@@ -276,6 +275,7 @@
 
 slave-bin.000002	#	Table_map	#	#	table_id: # (test.t2)
 
 slave-bin.000002	#	Write_rows_v1	#	#	table_id: # flags: STMT_END_F
 
 slave-bin.000002	#	Xid	#	#	COMMIT /* XID */
 
+slave-bin.000002	#	Binlog_checkpoint	#	#	slave-bin.000002
 
 include/check_slave_is_running.inc
 
 show binlog events in 'slave-bin.000005' from 4;
 
 ERROR HY000: Error when executing command SHOW BINLOG EVENTS: Could not find target log
 
 
 
mysqltest: Result content mismatch

Comment by Michael Widenius [ 2017-12-03 ]

Problem is that Binlog_checkpoint can happen at random times.

Fixed by not write binlog_checkpoint for the rpl_log test.

This also fixes failures in rpl_row_log and rpl_stmt_log

Comment by Michael Widenius [ 2017-12-03 ]

Fixed and pushed into 10.1

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