[MDEV-16272] rpl.rpl_semisync_ali_issues failed in buildbot with wrong result Created: 2018-05-23  Updated: 2021-01-12  Resolved: 2021-01-12

Status: Closed
Project: MariaDB Server
Component/s: Replication, Tests
Affects Version/s: 10.3, 10.4, 10.5
Fix Version/s: 10.3.28, 10.4.18, 10.5.9

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Andrei Elkin
Resolution: Fixed Votes: 1
Labels: None


 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/12946

rpl.rpl_semisync_ali_issues 'innodb,stmt' w1 [ fail ]
 
        Test ended at 2018-05-22 17:43:28
 
 
 
CURRENT_TEST: rpl.rpl_semisync_ali_issues
 
--- /mnt/buildbot/build/mariadb-10.3.7/mysql-test/suite/rpl/r/rpl_semisync_ali_issues.result	2018-05-22 12:59:12.000000000 +0300
 
+++ /mnt/buildbot/build/mariadb-10.3.7/mysql-test/suite/rpl/r/rpl_semisync_ali_issues.reject	2018-05-22 17:43:28.000000000 +0300
 
@@ -32,7 +32,7 @@
 
 show status like 'rpl_semi_sync_slave%';
 
 Variable_name	Value
 
 Rpl_semi_sync_slave_send_ack	0
 
-Rpl_semi_sync_slave_status	ON
 
+Rpl_semi_sync_slave_status	OFF
 
 connection master;
 
 CREATE TABLE t1(a INT) ENGINE=InnoDB;
 
 connection slave;
 
 
 
mysqltest: Result length mismatch



 Comments   
Comment by Sachin Setiya (Inactive) [ 2019-05-11 ]

I got a same failure but on very different line

CURRENT_TEST: rpl.rpl_semisync_ali_issues                                                                                                                      
--- /home/sachin/10.3/server/mysql-test/suite/rpl/r/rpl_semisync_ali_issues.result      2019-05-07 14:00:12.458433053 +0530                                    
+++ /home/sachin/10.3/server/mysql-test/suite/rpl/r/rpl_semisync_ali_issues.reject      2019-05-11 16:47:17.437417152 +0530                                    
@@ -32,7 +32,7 @@                                                                                                                                              
 show status like 'rpl_semi_sync_slave%';                                                                                                                      
 Variable_name  Value                                                                                                                                          
 Rpl_semi_sync_slave_send_ack   0                                                                                                                              
-Rpl_semi_sync_slave_status     ON                                                                                                                             
+Rpl_semi_sync_slave_status     OFF                                                                                                                            
 connection master;                                                                                                                                            
 CREATE TABLE t1(a INT) ENGINE=InnoDB;                                                                                                                         
 connection slave;                                                                                                                                             
                                                                                                                                                               
mysqltest: Result length mismatch

Comment by Sachin Setiya (Inactive) [ 2019-05-11 ]

I fixed it with this commit

commit 0d7c43cf5653454b90397838dccacfa5cbc8345e
 
Author: Sachin <sachin.setiya@mariadb.com>
 
Date:   Sat May 11 17:09:26 2019 +0530
 
 
 
    MDEV-16272 rpl.rpl_semisync_ali_issues failed in buildbot with wrong result
 
    
    Since start slave does wait for slave to start , Add a wait condition to
 
    confirm that slave is started.
 
 
 
diff --git a/mysql-test/suite/rpl/r/rpl_semisync_ali_issues.result b/mysql-test/suite/rpl/r/rpl_semisync_ali_issues.result
 
index 9607e8a7998..0468095a3dd 100644
 
--- a/mysql-test/suite/rpl/r/rpl_semisync_ali_issues.result
 
+++ b/mysql-test/suite/rpl/r/rpl_semisync_ali_issues.result
 
@@ -29,6 +29,7 @@ connection slave;
 
 stop slave;
 
 set global rpl_semi_sync_slave_enabled = 1;
 
 start slave;
 
+include/wait_for_slave_to_start.inc
 
 show status like 'rpl_semi_sync_slave%';
 
 Variable_name	Value
 
 Rpl_semi_sync_slave_send_ack	0
 
diff --git a/mysql-test/suite/rpl/t/rpl_semisync_ali_issues.test b/mysql-test/suite/rpl/t/rpl_semisync_ali_issues.test
 
index 52cd9e31753..ad5c5911ed6 100644
 
--- a/mysql-test/suite/rpl/t/rpl_semisync_ali_issues.test
 
+++ b/mysql-test/suite/rpl/t/rpl_semisync_ali_issues.test
 
@@ -31,6 +31,7 @@ echo [ enable semi-sync on slave ];
 
 stop slave;
 
 set global rpl_semi_sync_slave_enabled = 1;
 
 start slave;
 
+--source include/wait_for_slave_to_start.inc
 
 show status like 'rpl_semi_sync_slave%';
 
 
 connection master;

Comment by Sachin Setiya (Inactive) [ 2019-05-11 ]

Elkin , Okay to push after merge of mine and your patch

Comment by Alice Sherepa [ 2020-09-23 ]

recently on 10.3 http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/24716/steps/mtr_nm/logs/stdio

latest failures
Generated at Thu Feb 08 08:27:40 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.