Bug #94149 main.mysqldump fails due to out of data reason
Submitted: 31 Jan 2019 8:28 Modified: 1 Feb 2019 5:12
Reporter: yuhui wang Email Updates:
Status: Duplicate Impact on me:
None 
Category:Tools: MTR / mysql-test-run Severity:S7 (Test Cases)
Version:8.0.14 OS:CentOS
Assigned to: CPU Architecture:x86
Tags: main, mtr, mysqldump, testcase

[31 Jan 2019 8:28] yuhui wang
Description:
main.mysqldump fails under both release and debug version.
The root cause is that the following sql which is out of data:
create event ee2 on schedule at '2018-12-31 21:01:23' do set @a=5;

Now it is year 2019, while this sql still writes 2018 which will make testcase fail by following error:

+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;

How to repeat:
./mtr main.mysqldump

Suggested fix:
$ git diff t/mysqldump.test
diff --git a/mysql-test/t/mysqldump.test b/mysql-test/t/mysqldump.test
index f3c4fa2..419f5e9 100644
--- a/mysql-test/t/mysqldump.test
+++ b/mysql-test/t/mysqldump.test
@@ -1728,7 +1728,7 @@ show create event ee1;

 ## prove three works (with spaces and tabs on the end)
 # start with one from the previous restore
-create event ee2 on schedule at '2018-12-31 21:01:23' do set @a=5;
+create event ee2 on schedule at '2030-12-31 22:01:23' do set @a=5;
 create event ee3 on schedule at '2030-12-31 22:01:23' do set @a=5;
 show events;
 --exec $MYSQL_DUMP --events second > $MYSQLTEST_VARDIR/tmp/bug16853-2.sql

Just change the datatime.
[1 Feb 2019 5:12] MySQL Verification Team
Hello yuhui,

Thank you for the report and test case.
Imho this is duplicate of Bug #93788, please see Bug #93788

regards,
Umesh