| Bug #91020 | group_replication.gr_blocked_start_gr_killed always failing warning check | ||
|---|---|---|---|
| Submitted: | 25 May 2018 7:41 | Modified: | 4 Dec 2018 12:25 |
| Reporter: | Laurynas Biveinis (OCA) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Tests: Group Replication | Severity: | S3 (Non-critical) |
| Version: | 8.0.11 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | gr, mtr | ||
[25 May 2018 8:16]
MySQL Verification Team
Hello Laurynas, Thank you for the report and feedback! Thanks, Umesh
[4 Dec 2018 12:25]
David Moss
Posted by developer: Seems to be related to internal testing only, closing without change log entry
Description: group_replication.gr_blocked_start_gr_killed w2 [ fail ] Found warnings/errors in server log file! Test ended at 2018-05-24 11:06:20 line 2018-05-24T11:05:46.250951Z 213 [ERROR] [MY-011071] [Server] Disk is full writing './server-relay-log-group_replication_applier.~rec~' (OS errno 28 - No space left on device). Waiting for someone to free space... ^ Found warnings in /mnt/workspace/mysql-5.7-param/BUILD_TYPE/debug/Host/min-trusty-x64/build/mysql-test/var/2/log/mysqld.1.err ok How to repeat: ./mtr --debug-server --suite=group_replication gr_blocked_start_gr_killed --big-test Suggested fix: The testcase has CALL mtr.add_suppression("Disk is full writing.*(Errcode: 28 - No space left on device)"); The fix probably would be "s/Errcode/OS errno" in the above