Bug #37940 rpl_dual_pos_advance fails on pushbuild,fail wait_for_slave_to_stop

• Submitted: 7 Jul 2008 16:50
• Modified: 11 Jul 2008 18:15
• Reporter: Sven Sandberg
• Status: Closed
• Category: Tests: Replication
• Severity: S7 (Test Cases)
• Version: 6.0-rpl
• OS: Any
• Assigned to: Mats Kindahl
• CPU Architecture: Any
• Tags: pushbuild, rpl_dual_pos_advance, test failure, wait_for_slave_to_stop

[7 Jul 2008 16:50] Sven Sandberg

Description:
rpl_dual_pos_advance fails sporadically in pushbuild with this error:

rpl.rpl_dual_pos_advance       [ fail ]

CURRENT_TEST: rpl.rpl_dual_pos_advance
--- /data0/pushbuild/pb2/pb/bzr_mysql-6.0-rpl/14/mysql-6.0.6-alpha-pb14/mysql-test/suite/rpl/r/rpl_dual_pos_advance.result	2008-06-22 23:29:22.000000000 +0300
+++ /data0/pushbuild/pb2/pb/bzr_mysql-6.0-rpl/14/mysql-6.0.6-alpha-pb14/mysql-test/suite/rpl/r/rpl_dual_pos_advance.reject	2008-06-23 01:08:08.725158667 +0300
@@ -9,52 +9,43 @@
 start slave;
 create table t1 (n int);
 stop slave;
-create table t2 (n int);
-show tables;
-Tables_in_test
-t1
-t2
-create table t3 (n int) engine=innodb;
-set @a=1;
-insert into t3 values(@a);
-begin;
-insert into t3 values(2);
-insert into t3 values(3);
-commit;
-insert into t3 values(4);
-start slave until master_log_file="slave-bin.000001",master_log_pos=195;
-Warnings:
-Note	1278	It is recommended to use --skip-slave-start when doing step-by-step replication with START SLAVE UNTIL; otherwise, you will get problems if you get an unexpected slave's mysqld restart
-show tables;
-Tables_in_test
-t1
-t2
-start slave until master_log_file="slave-bin.000001",master_log_pos=438;
-Warnings:
-Note	1278	It is recommended to use --skip-slave-start when doing step-by-step replication with START SLAVE UNTIL; otherwise, you will get problems if you get an unexpected slave's mysqld restart
-select * from t3;
-n
-1
-start slave until master_log_file="slave-bin.000001",master_log_pos=663;
-Warnings:
-Note	1278	It is recommended to use --skip-slave-start when doing step-by-step replication with START SLAVE UNTIL; otherwise, you will get problems if you get an unexpected slave's mysqld restart
-select * from t3;
-n
-1
-2
-3
-start slave;
-create table t4 (n int);
-create table t5 (n int);
-create table t6 (n int);
-show tables;
-Tables_in_test
-t1
-t2
-t3
-t4
-t5
-t6
-stop slave;
-reset slave;
-drop table t1,t2,t3,t4,t5,t6;
+"Failed while waiting for slave to stop"
+SHOW SLAVE STATUS;
+Slave_IO_State	#
+Master_Host	127.0.0.1
+Master_User	root
+Master_Port	MASTER_PORT
+Connect_Retry	1
+Master_Log_File	master-bin.000001
+Read_Master_Log_Pos	#
+Relay_Log_File	#
+Relay_Log_Pos	#
+Relay_Master_Log_File	master-bin.000001
+Slave_IO_Running	Yes
+Slave_SQL_Running	Yes
+Replicate_Do_DB	
+Replicate_Ignore_DB	
+Replicate_Do_Table	
+Replicate_Ignore_Table	
+Replicate_Wild_Do_Table	
+Replicate_Wild_Ignore_Table	
+Last_Errno	0
+Last_Error	
+Skip_Counter	0
+Exec_Master_Log_Pos	#
+Relay_Log_Space	#
+Until_Condition	None
+Until_Log_File	
+Until_Log_Pos	0
+Master_SSL_Allowed	No
+Master_SSL_CA_File	
+Master_SSL_CA_Path	
+Master_SSL_Cert	
+Master_SSL_Cipher	
+Master_SSL_Key	
+Seconds_Behind_Master	#
+Master_SSL_Verify_Server_Cert	No
+Last_IO_Errno	0
+Last_IO_Error	
+Last_SQL_Errno	0
+Last_SQL_Error	

mysqltest: In included file "./include/wait_for_slave_to_stop.inc": Result content mismatch

Stopping all servers...
Saving datadirs...
 - saving '/dev/shm/var-n_mix-110/mysqld.1'
 - saving '/dev/shm/var-n_mix-110/mysqld.2'
Resuming tests...

Retrying, attempt(1/3)...

Restarting all servers

How to repeat:
e.g., here:
https://intranet.mysql.com/secure/pushbuild/showpush.pl?dir=bzr_mysql-6.0-rpl&order=14
'sapsrv1' Autopush/n_mix

But also on many other places. See also xref: http://tinyurl.com/6dezzt

Note that it only failed in 6.0-rpl

[9 Jul 2008 14:18] Mats Kindahl

The test fails consistently, not sporadically, on all major platforms and configurations. The test was wrongly written to include 'include/wait_for_slave_to_stop.inc' after issuing a STOP SLAVE on *master*. However, the included file has a 'connection slave' as first line, causing it to wait for the *slave* to stop, which will never happen since the slave is running happily along.

See BUG#37941 as well.

[11 Jul 2008 18:15] Paul DuBois

Test case change. No changelog entry needed.

[30 Jan 2009 13:32] Bugs System

Pushed into 6.0.10-alpha (revid:[e-mail]-20090129165607-wiskabxm948yx463) (version source revid:[e-mail]-20090129163120-e2ntks4wgpqde6zt) (merge vers: 6.0.10-alpha) (pib:6)

[30 Jan 2009 15:11] Bugs System

Pushed into 5.1.32 (revid:[e-mail]-20090129165946-d6jnnfqfokuzr09y) (version source revid:[e-mail]-20080708162102-qbyxyqv4g1kc5seg) (merge vers: 5.1.28) (pib:6)

[17 Feb 2009 15:01] Bugs System

Pushed into 5.1.32-ndb-6.3.23 (revid:[e-mail]-20090217131017-6u8qz1edkjfiobef) (version source revid:[e-mail]-20090203133556-9rclp06ol19bmzs4) (merge vers: 5.1.32-ndb-6.3.22) (pib:6)

[17 Feb 2009 16:49] Bugs System

Pushed into 5.1.32-ndb-6.4.3 (revid:[e-mail]-20090217134419-5ha6xg4dpedrbmau) (version source revid:[e-mail]-20090203133556-9rclp06ol19bmzs4) (merge vers: 5.1.32-ndb-6.3.22) (pib:6)

[17 Feb 2009 18:25] Bugs System

Pushed into 5.1.32-ndb-6.2.17 (revid:[e-mail]-20090217134216-5699eq74ws4oxa0j) (version source revid:[e-mail]-20090201210519-vehobc4sy3g9s38e) (merge vers: 5.1.32-ndb-6.2.17) (pib:6)