[MDEV-14366] rpl.rpl_semi_sync_after_sync, rpl.rpl_semi_sync_after_sync_row failed in buildbot with wrong result Created: 2017-11-10  Updated: 2021-01-12  Resolved: 2021-01-12

Status: Closed
Project: MariaDB Server
Component/s: Replication, Tests
Affects Version/s: 10.1, 10.2
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Andrei Elkin
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MDEV-22008 rpl.rpl_semi_sync fails with wrong v... Closed
Relates
relates to MDEV-11220 rpl.rpl_semi_sync failed in buildbot,... Closed
relates to MDEV-21031 rpl_semi_sync_after_sync_row result m... Closed

 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-deb-jessie-amd64/builds/2858/steps/mtr/logs/stdio

rpl.rpl_semi_sync_after_sync_row 'innodb_plugin,row' w1 [ fail ]
        Test ended at 2017-09-27 10:09:42
 
CURRENT_TEST: rpl.rpl_semi_sync_after_sync_row
--- /usr/share/mysql/mysql-test/suite/rpl/r/rpl_semi_sync_after_sync_row.result	2017-09-27 08:07:47.000000000 -0400
+++ /dev/shm/var/1/log/rpl_semi_sync_after_sync_row.reject	2017-09-27 10:09:41.559456813 -0400
@@ -228,7 +228,7 @@
 [ master status should be ON again after slave catches up ]
 show status like 'Rpl_semi_sync_master_status';
 Variable_name	Value
-Rpl_semi_sync_master_status	ON
+Rpl_semi_sync_master_status	OFF
 show status like 'Rpl_semi_sync_master_no_tx';
 Variable_name	Value
 Rpl_semi_sync_master_no_tx	12
 
mysqltest: Result length mismatch



 Comments   
Comment by Elena Stepanova [ 2017-12-20 ]

rpl.rpl_semi_sync_after_sync
http://buildbot.askmonty.org/buildbot/builders/kvm-deb-trusty-amd64/builds/8295/steps/mtr/logs/stdio

rpl.rpl_semi_sync_after_sync 'innodb_plugin,stmt' w4 [ fail ]
        Test ended at 2017-11-22 00:28:25
 
CURRENT_TEST: rpl.rpl_semi_sync_after_sync
--- /usr/share/mysql/mysql-test/suite/rpl/r/rpl_semi_sync_after_sync.result	2017-11-21 21:30:53.000000000 +0000
+++ /run/shm/var/4/log/rpl_semi_sync_after_sync.reject	2017-11-22 00:28:25.443781258 +0000
@@ -228,7 +228,7 @@
 [ master status should be ON again after slave catches up ]
 show status like 'Rpl_semi_sync_master_status';
 Variable_name	Value
-Rpl_semi_sync_master_status	ON
+Rpl_semi_sync_master_status	OFF
 show status like 'Rpl_semi_sync_master_no_tx';
 Variable_name	Value
 Rpl_semi_sync_master_no_tx	12
@@ -250,10 +250,10 @@
 [ Semi-sync master status variables before FLUSH STATUS ]
 SHOW STATUS LIKE 'Rpl_semi_sync_master_no_tx';
 Variable_name	Value
-Rpl_semi_sync_master_no_tx	12
+Rpl_semi_sync_master_no_tx	13
 SHOW STATUS LIKE 'Rpl_semi_sync_master_yes_tx';
 Variable_name	Value
-Rpl_semi_sync_master_yes_tx	17
+Rpl_semi_sync_master_yes_tx	16
 FLUSH NO_WRITE_TO_BINLOG STATUS;
 [ Semi-sync master status variables after FLUSH STATUS ]
 SHOW STATUS LIKE 'Rpl_semi_sync_master_no_tx';
 
mysqltest: Result length mismatch

Comment by Alice Sherepa [ 2020-09-11 ]

on 10.3 http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos73-ppc64/builds/14178/steps/mtr/logs/stdio

rpl.rpl_semi_sync_after_sync_row 'innodb,row' w4 [ fail ]
        Test ended at 2020-09-02 04:52:35
 
CURRENT_TEST: rpl.rpl_semi_sync_after_sync_row
--- /usr/share/mysql-test/suite/rpl/r/rpl_semi_sync_after_sync_row.result	2020-09-01 23:36:18.000000000 +0000
+++ /dev/shm/var/4/log/rpl_semi_sync_after_sync_row.reject	2020-09-02 04:52:34.560071145 +0000
@@ -407,7 +407,7 @@
 [ Semi-sync status on master should be ON ]
 show status like 'Rpl_semi_sync_master_clients';
 Variable_name	Value
-Rpl_semi_sync_master_clients	0
+Rpl_semi_sync_master_clients	1
 show status like 'Rpl_semi_sync_master_status';
 Variable_name	Value
 Rpl_semi_sync_master_status	ON
 
mysqltest: Result content mismatch

Generated at Thu Feb 08 08:12:59 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.