Bug #87313 Test auth_sec.secure_file_priv_warnings handling server error log incorrectly

• Submitted: 4 Aug 2017 3:45
• Modified: 8 Aug 2017 13:07
• Reporter: Laurynas Biveinis (OCA)
• Status: Closed
• Category: MySQL Server: Tests
• Severity: S3 (Non-critical)
• OS: Any
• CPU Architecture: Any
• Tags: mtr

[4 Aug 2017 3:45] Laurynas Biveinis

Description:
Testcase auth_sec.secure_file_priv_warnings does several things wrong with the server error log:
- greps it without restarting with a custom log location first, enabling false positives as the log contains everything from the past testcases on the same MTR worker;
- deletes it, destroying content from all the past testcases on the same MTR worker, and also destroying the CURRENT_TEST marker in the log which MTR uses;
- restarts with the same error log location, requiring a cumbersome perl script to delete it in a loop.

Found on 8.0.2, but should be present in lower versions too.

How to repeat:
See above

Suggested fix:
I will upload later

[4 Aug 2017 8:53] MySQL Verification Team

Hello Laurynas,

Thank you for the report and feedback!

Thanks,
Umesh

[5 Aug 2017 7:35] Laurynas Biveinis

Bug 87313 fix for 8.0.2

(*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Contribution: bug87313-8.0.2.patch (application/octet-stream, text), 5.72 KiB.

[8 Aug 2017 13:07] Paul DuBois

Posted by developer:
 
Fixed in 8.0.3.

The main.mysql_upgrade_grant, main.roles-upgrade, and
auth_sec.secure_file_priv_warnings, test cases mishandled the error
log. Thanks to Laurynas Biveinis for the patch.