MDEV-15238 rpl.perf_buildin_semisync_issue40 sporadically fails on BB

The test was used to result in mismatch due to unaccounted specifics of the master-slave handshake protocol that sets the Slave_IO_Running status to true while the semisync master status is set to active a bit later. The test is refined to expect that.
MariaDB · Feb 7, 2018 · 7bcf5e2 · 7bcf5e2
1 parent 029ab11
commit 7bcf5e2
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 0 deletions.
diff --git a/...pl/r/perf_buildin_semisync_issue40.result → ...uite/rpl/r/rpl_semisync_ali_issues.result b/...pl/r/perf_buildin_semisync_issue40.result → ...uite/rpl/r/rpl_semisync_ali_issues.result
diff --git a/.../perf_buildin_semisync_issue40-master.opt → .../rpl/t/rpl_semisync_ali_issues-master.opt b/.../perf_buildin_semisync_issue40-master.opt → .../rpl/t/rpl_semisync_ali_issues-master.opt
diff --git a/...t/perf_buildin_semisync_issue40-slave.opt → ...e/rpl/t/rpl_semisync_ali_issues-slave.opt b/...t/perf_buildin_semisync_issue40-slave.opt → ...e/rpl/t/rpl_semisync_ali_issues-slave.opt
diff --git a/.../rpl/t/perf_buildin_semisync_issue40.test → .../suite/rpl/t/rpl_semisync_ali_issues.test b/.../rpl/t/perf_buildin_semisync_issue40.test → .../suite/rpl/t/rpl_semisync_ali_issues.test
@@ -210,6 +210,10 @@ START SLAVE IO_THREAD;
 --source include/wait_for_slave_io_to_start.inc
 
 connection con1;
+--let $status_var= Rpl_semi_sync_master_status
+--let $status_var_value=ON
+--source include/wait_for_status_var.inc
+
 SET GLOBAL rpl_semi_sync_master_timeout= 10000000;
 SET GLOBAL rpl_semi_sync_master_wait_no_slave= 1;
 INSERT INTO t1 values (4);