[MDEV-15238] rpl.perf_buildin_semisync_issue40 sporadically fails on BB Created: 2018-02-07  Updated: 2018-02-14  Resolved: 2018-02-14

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.3
Fix Version/s: 10.3.5

Type: Bug Priority: Minor
Reporter: Andrei Elkin Assignee: Andrei Elkin
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-13073 AliSQL: [Performance] Issue #40 Optim... Closed

 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.



 Comments   
Comment by Andrei Elkin [ 2018-02-14 ]

Pushed commit 7bcf5e2907db6a8f.

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