Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.3
-
None
Description
The test fails having the following trace:
rpl.perf_buildin_semisync_issue40 'innodb,row' w2 [ fail ] Test ended at 2018-02-06 19:52:28 CURRENT_TEST: rpl.perf_buildin_semisync_issue40 — /mnt/buildbot/build/mariadb-10.3.5/mysql-test/suite/rpl/r/perf_buildin_semisync_issue40.result 2018-02-06 17:28:26.000000000 +0200 +++ /mnt/buildbot/build/mariadb-10.3.5/mysql-test/suite/rpl/r/perf_buildin_semisync_issue40.reject 2018-02-06 19:52:28.000000000 +0200 @@ -204,7 +204,7 @@ connection con1; 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_clients'; Variable_name Value Rpl_semi_sync_master_clients 1 mysqltest: Result length mismatch
By this report time the case has been already analyzed and fixed locally.
Attachments
Issue Links
- relates to
-
MDEV-13073 AliSQL: [Performance] Issue #40 Optimize performance of semisync
-
- Closed
-