Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Duplicate
-
10.1(EOL), 10.2(EOL)
-
None
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
|
Attachments
Issue Links
- duplicates
-
MDEV-22008 rpl.rpl_semi_sync fails with wrong value for Rpl_semi_sync_master_clients
- Closed
- relates to
-
MDEV-11220 rpl.rpl_semi_sync failed in buildbot, result mismatch, Rpl_semi_sync_master_status on/off
- Closed
-
MDEV-21031 rpl_semi_sync_after_sync_row result mismatch
- Closed