Bug #91175 rpl_semi_sync_group_commit_deadlock.test is not simulating flush error

• Submitted: 7 Jun 2018 12:36
• Modified: 19 Jun 2018 12:27
• Reporter: zhang xiaojian
• Status: Verified
• Category: MySQL Server: Tests
• Severity: S3 (Non-critical)
• Version: 5.7.22
• OS: Linux
• CPU Architecture: Any

[7 Jun 2018 12:36] zhang xiaojian

Description:
There are two similar testcases: rpl_group_commit_deadlock  and rpl_semi_sync_group_commit_deadlock. one for normal replication and the other for semi-sync.

rpl_group_commit_deadlock simulate flush error by :

--let $error_simulation= 1

But rpl_semi_sync_group_commit_deadlock :

--let $error_simulation= 0

and in rpl_semi_sync_group_commit_deadlock.test's comment, there should be a simulating flush error.

so, does rpl_semi_sync_group_commit_deadlock have a simulating flush error ?

Problem is : In debug mode, if error_simulation=1 the rpl_semi_sync_group_commit_deadlock will cause a crash.

How to repeat:
In rpl_semi_sync_group_commit_deadlock.test ,  set:

--let $error_simulation= 1

and run the testcase:

./mtr rpl_semi_sync_group_commit_deadlock

will have a crash by assert error.

Suggested fix:
None

[19 Jun 2018 12:27] MySQL Verification Team

Hello!

Thank you for the report!

Thanks,
Umesh