Bug #78899 | main.events_1 mysql test fails | ||
---|---|---|---|
Submitted: | 21 Oct 2015 13:50 | Modified: | 21 Oct 2015 19:12 |
Reporter: | Richard Prohaska | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Tests | Severity: | S3 (Non-critical) |
Version: | 5.7.9, 5.7.8 | OS: | Ubuntu (14.04) |
Assigned to: | CPU Architecture: | Any |
[21 Oct 2015 13:50]
Richard Prohaska
[21 Oct 2015 14:06]
MySQL Verification Team
Hello Richard Prohaska, Thank you for the report. Thanks, Umesh
[21 Oct 2015 14:07]
MySQL Verification Team
// 5.7.9 // 5.7.9 [umshastr@hod03]/export/umesh/server/binaries/mysql-advanced-5.7.9-linux-glibc2.5-x86_64/mysql-test: cat ../docs/INFO_SRC commit: 0efebb1df63491b46ab6f77956a6aaec509ef015 date: 2015-10-09 12:33:31 +0200 build-date: 2015-10-12 08:11:42 +0200 short: 0efebb1 branch: mysql-5.7.9-release MySQL source 5.7.9 [umshastr@hod03]/export/umesh/server/binaries/mysql-advanced-5.7.9-linux-glibc2.5-x86_64/mysql-test: ./mtr main.events_1 Logging: ./mtr main.events_1 MySQL Version 5.7.9 Too long tmpdir path '/export/umesh/server/binaries/mysql-advanced-5.7.9-linux-glibc2.5-x86_64/mysql-test/var/tmp' creating a shorter one... - using tmpdir: '/tmp/YPjumkAlvd' Checking supported features... - SSL connections supported Collecting tests... Removing old var directory... Creating var directory '/export/umesh/server/binaries/mysql-advanced-5.7.9-linux-glibc2.5-x86_64/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.events_1 [ fail ] Test ended at 2015-10-21 16:05:32 CURRENT_TEST: main.events_1 mysqltest: At line 133: query 'drop event event3' failed: 1539: Unknown event 'event3' The result from queries just before the failure was: < snip > drop table non_qualif; alter event non_existant rename to non_existant_too; ERROR HY000: Unknown event 'non_existant' set global event_scheduler = off; create event existant on schedule at now() + interval 1 year do select 12; alter event non_existant rename to existant; ERROR HY000: Event 'existant' already exists alter event existant rename to events_test.existant; ERROR HY000: Same old and new event name drop event existant; create table t_event3 (a int, b float); drop event if exists event3; Warnings: Note 1305 Event event3 does not exist create event event3 on schedule every 50 + 10 minute starts date_add("20100101", interval 5 minute) ends date_add("20151010", interval 5 day) comment "portokala_comment" DO insert into t_event3 values (unix_timestamp(), rand()); Warnings: Note 1588 Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation. select count(*) from t_event3; count(*) 0 safe_process[32555]: Child process: 32556, exit: 1 - the logfile can be found in '/export/umesh/server/binaries/mysql-advanced-5.7.9-linux-glibc2.5-x86_64/mysql-test/var/log/main.events_1/events_1.log' -------------------------------------------------------------------------- The servers were restarted 0 times Spent 0.000 of 4 seconds executing testcases Completed: Failed 1/1 tests, 0.00% were successful. Failing test(s): main.events_1 The log files in var/log may give you some hint of what went wrong. If you want to report this error, please read first the documentation at http://dev.mysql.com/doc/mysql/en/mysql-test-suite.html mysql-test-run: *** ERROR: there were failing test cases
[21 Oct 2015 14:08]
MySQL Verification Team
// 5.7.8 [umshastr@hod03]/export/umesh/server/binaries/mysql-5.7.8-rc/mysql-test: cat ../docs/INFO_SRC commit: ae3b133e5f7b13d1edf7acf7eee6af2c2b4014e2 date: 2015-07-20 14:02:16 +0200 build-date: 2015-07-20 14:16:07 +0200 short: ae3b133 branch: mysql-5.7.8-rc-release MySQL source 5.7.8 [umshastr@hod03]/export/umesh/server/binaries/mysql-5.7.8-rc/mysql-test: ./mtr main.events_1 Logging: ./mtr main.events_1 MySQL Version 5.7.8 Checking supported features... - SSL connections supported Collecting tests... Checking leftover processes... Removing old var directory... Creating var directory '/export/umesh/server/binaries/mysql-5.7.8-rc/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.events_1 [ fail ] Test ended at 2015-10-21 16:02:27 CURRENT_TEST: main.events_1 mysqltest: At line 133: query 'drop event event3' failed: 1539: Unknown event 'event3' The result from queries just before the failure was: < snip > drop table non_qualif; alter event non_existant rename to non_existant_too; ERROR HY000: Unknown event 'non_existant' set global event_scheduler = off; create event existant on schedule at now() + interval 1 year do select 12; alter event non_existant rename to existant; ERROR HY000: Event 'existant' already exists alter event existant rename to events_test.existant; ERROR HY000: Same old and new event name drop event existant; create table t_event3 (a int, b float); drop event if exists event3; Warnings: Note 1305 Event event3 does not exist create event event3 on schedule every 50 + 10 minute starts date_add("20100101", interval 5 minute) ends date_add("20151010", interval 5 day) comment "portokala_comment" DO insert into t_event3 values (unix_timestamp(), rand()); Warnings: Note 1588 Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation. select count(*) from t_event3; count(*) 0 safe_process[32071]: Child process: 32072, exit: 1 - the logfile can be found in '/export/umesh/server/binaries/mysql-5.7.8-rc/mysql-test/var/log/main.events_1/events_1.log' -------------------------------------------------------------------------- The servers were restarted 0 times Spent 0.000 of 3 seconds executing testcases Completed: Failed 1/1 tests, 0.00% were successful. Failing test(s): main.events_1 The log files in var/log may give you some hint of what went wrong. If you want to report this error, please read first the documentation at http://dev.mysql.com/doc/mysql/en/mysql-test-suite.html mysql-test-run: *** ERROR: there were failing test cases
[21 Oct 2015 19:12]
Erlend Dahl
This has been fixed in the upcoming 5.7.10 release (and in 5.5.47, 5.6.28 and 5.8.0).