Bug #98080 mtr test failed for mysqldump case in 5.5.62
Submitted: 27 Dec 2019 3:09 Modified: 7 Jan 2020 11:37
Reporter: jibin ge Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Server: Tests Severity:S7 (Test Cases)
Version:5.5.62 OS:CentOS
Assigned to: CPU Architecture:Any

[27 Dec 2019 3:09] jibin ge
Description:
./mysql-test-run main.mysqldump
Logging: ./mysql-test-run  main.mysqldump
191227 10:52:55 [Warning] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
191227 10:52:55 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.5.62-debug) starting as process 15438 ...
MySQL Version 5.5.62
Checking supported features...
 - SSL connections supported
 - binaries are debug compiled
Collecting tests...
Removing old var directory...
Creating var directory '/usr/local/mysql/mysql-test/var'...
Installing system database...

==============================================================================

TEST                                      RESULT   TIME (ms) or COMMENT
--------------------------------------------------------------------------

worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 13000..13009
main.mysqldump                           [ fail ]
        Test ended at 2019-12-27 10:53:04

CURRENT_TEST: main.mysqldump
mysqldump: Couldn't find table: "non_existing"
mysqldump: Got error: 1356: View 'test.v1' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them when using LOCK TABLES
mysqldump: Couldn't execute 'SHOW FIELDS FROM `v1`': View 'test.v1' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them (1356)
-- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly.
mysqldump: Got error: 1083: Field separator argument is not what is expected; check the manual when executing 'SELECT INTO OUTFILE'
mysqldump: Got error: 1083: Field separator argument is not what is expected; check the manual when executing 'SELECT INTO OUTFILE'
mysqldump: Got error: 1083: Field separator argument is not what is expected; check the manual when executing 'SELECT INTO OUTFILE'
mysqldump: user2 has insufficent privileges to SHOW CREATE PROCEDURE `sp1`!
mysqldump: Got error: 1146: Table 'test.???????????????????????' doesn't exist when using LOCK TABLES
-- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly.
-- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly.
mysqldump: Got error: 1083: Field separator argument is not what is expected; check the manual when executing 'SELECT INTO OUTFILE'
mysqldump: Got error: 1083: Field separator argument is not what is expected; check the manual when executing 'SELECT INTO OUTFILE'
mysqldump: user1 has insufficent privileges to SHOW CREATE FUNCTION `hello1`!
-- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly.
--- /usr/local/mysql/mysql-test/r/mysqldump.result	2018-08-29 00:12:51.000000000 +0300
+++ /usr/local/mysql/mysql-test/r/mysqldump.reject	2019-12-27 05:53:04.109006868 +0300
@@ -4234,11 +4234,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    latin1	latin1_swedish_ci	latin1_swedish_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_clientcollation_connection	Database Collation
 second	ee1	root@localhost	UTC	ONE TIME	2035-12-31 20:01:23	NULL	NULL	NULL	NULL	ENABLED	1	latin1	latin1_swedish_ci   latin1_swedish_ci
-second	ee2	root@localhost	UTC	ONE TIME	2018-12-31 21:01:23	NULL	NULL	NULL	NULL	ENABLED	1	latin1	latin1_swedish_ci   latin1_swedish_ci
 second	ee3	root@localhost	UTC	ONE TIME	2030-12-31 22:01:23	NULL	NULL	NULL	NULL	ENABLED	1	latin1	latin1_swedish_ci   latin1_swedish_ci
 drop database second;
 create database third;
@@ -4246,7 +4247,6 @@
 show events;
 Db	Name	Definer	Time zone	Type	Execute at	Interval value	Interval field	Starts	Ends	Status	Originator	character_set_clientcollation_connection	Database Collation
 third	ee1	root@localhost	UTC	ONE TIME	2035-12-31 20:01:23	NULL	NULL	NULL	NULL	ENABLED	1	latin1	latin1_swedish_ci   latin1_swedish_ci
-third	ee2	root@localhost	UTC	ONE TIME	2018-12-31 21:01:23	NULL	NULL	NULL	NULL	ENABLED	1	latin1	latin1_swedish_ci   latin1_swedish_ci
 third	ee3	root@localhost	UTC	ONE TIME	2030-12-31 22:01:23	NULL	NULL	NULL	NULL	ENABLED	1	latin1	latin1_swedish_ci   latin1_swedish_ci
 drop database third;
 set time_zone = 'SYSTEM';
mysqltest: Result content mismatch

 - saving '/usr/local/mysql/mysql-test/var/log/main.mysqldump/' to '/usr/local/mysql/mysql-test/var/log/main.mysqldump/'
--------------------------------------------------------------------------
The servers were restarted 0 times
Spent 0.000 of 9 seconds executing testcases

Completed: Failed 1/1 tests, 0.00% were successful.

Failing test(s): main.mysqldump

How to repeat:
./mysql-test-run main.mysqldump
[27 Dec 2019 4:28] MySQL Verification Team
Hello jibin ge,

Thank you for the report and feedback.
Verified as described with 5.5.62 Generic Linux(binary tarball build).

regards,
Umesh
[7 Jan 2020 11:37] Erlend Dahl
Posted by developer:
 
5.5 was EOL as of January 20, 2019.

The problem was fixed in 5.6 and upwards by

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