Bug #93788 main.mysqldump is failing because of dropped event
Submitted: 2 Jan 2019 23:34 Modified: 4 Jan 2019 13:27
Reporter: Manuel Ung Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Tests Severity:S7 (Test Cases)
Version:8.0.13, 5.7.24 OS:Any
Assigned to: CPU Architecture:Any

[2 Jan 2019 23:34] Manuel Ung
Description:
The main.mysqldump test is failing because it creates an event that executes on Dec 31, 2018. Since this is now in the pass, this event just gets dropped, and the test fails.

How to repeat:
Just run ./mtr main.mysqldump

You get:

@@ -3907,11 +3907,12 @@
 Event  sql_mode        time_zone       Create Event    character_set_client    collation_connection    Database Collation
 ee1            UTC     CREATE DEFINER=`root`@`localhost` EVENT `ee1` ON SCHEDULE AT '2035-12-31 20:01:23' ON COMPLETION NOT PRESERVE ENABLE DO set @a=5        utf8mb4 utf8mb4_0900_ai_ci      utf8mb4_0900_ai_ci
 create event ee2 on schedule at '2018-12-31 21:01:23' do set @a=5;
+Warnings:
+Note   1588    Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.
 create event ee3 on schedule at '2030-12-31 22:01:23' do set @a=5;
 show events;
 Db     Name    Definer Time zone       Type    Execute at      Interval value  Interval field  Starts  Ends    Status  Originator      character_set_client    collation_connection    Database Collation
 second ee1     root@localhost  UTC     ONE TIME        2035-12-31 20:01:23     NULL    NULL    NULL    NULL    ENABLED 1       utf8mb4 utf8mb4_0900_ai_ci      utf8mb4_0900_ai_ci
-second ee2     root@localhost  UTC     ONE TIME        2018-12-31 21:01:23     NULL    NULL    NULL    NULL    ENABLED 1       utf8mb4 utf8mb4_0900_ai_ci      utf8mb4_0900_ai_ci
 second ee3     root@localhost  UTC     ONE TIME        2030-12-31 22:01:23     NULL    NULL    NULL    NULL    ENABLED 1       utf8mb4 utf8mb4_0900_ai_ci      utf8mb4_0900_ai_ci
 drop database second;
 create database third;
@@ -3919,7 +3920,6 @@
 show events;
 Db     Name    Definer Time zone       Type    Execute at      Interval value  Interval field  Starts  Ends    Status  Originator      character_set_client    collation_connection    Database Collation
 third  ee1     root@localhost  UTC     ONE TIME        2035-12-31 20:01:23     NULL    NULL    NULL    NULL    ENABLED 1       utf8mb4 utf8mb4_0900_ai_ci      utf8mb4_0900_ai_ci
-third  ee2     root@localhost  UTC     ONE TIME        2018-12-31 21:01:23     NULL    NULL    NULL    NULL    ENABLED 1       utf8mb4 utf8mb4_0900_ai_ci      utf8mb4_0900_ai_ci
 third  ee3     root@localhost  UTC     ONE TIME        2030-12-31 22:01:23     NULL    NULL    NULL    NULL    ENABLED 1       utf8mb4 utf8mb4_0900_ai_ci      utf8mb4_0900_ai_ci
 drop database third;
 set time_zone = 'SYSTEM';

Suggested fix:
Update the date to sometime in the future.
[3 Jan 2019 4:58] MySQL Verification Team
Hello Manuel,

Thank you for the report and feedback.

regards,
Umesh
[3 Jan 2019 7:44] MySQL Verification Team
Bug #93792 marked as duplicate of this one
[3 Jan 2019 7:45] MySQL Verification Team
Bug #93793 marked as duplicate of this one
[3 Jan 2019 8:51] Laurynas Biveinis
5.6 is affected too
[4 Jan 2019 13:27] Erlend Dahl
Duplicate of fixed bug

Bug#93778 main.mysqldump fails with event created in the past