[MDEV-8951] main.event_1 test fails due to 2015-10-10 being insufficiently futuristic Created: 2015-10-16  Updated: 2015-10-21  Resolved: 2015-10-21

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.0.21, 5.5, 10.0
Fix Version/s: 5.5.47, 10.0.22

Type: Bug Priority: Major
Reporter: David Gow Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: None
Environment:

Linux 3.13 / x86_64


Sprint: 10.0.22

 Description   

Running main.events_1 has recently broken as "20151010" is no longer in the future:

Unknown macro: {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());}
Unknown macro: {Warnings}
Unknown macro: {Note 1588 Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.}
Unknown macro: {select count(*) from t_event3;}
Unknown macro: {count(*)}

Replacing "20151010" on line 128 of mysql-test/t/events_1.test to a later date (I used "20380101") fixes the issue. See https://github.com/MariaDB/server/blob/10.0/mysql-test/t/events_1.test#L128

This issue is also present in upstream MySQL.



 Comments   
Comment by Elena Stepanova [ 2015-10-20 ]

It has already been fixed in 10.1 (https://github.com/MariaDB/server/commit/7454f1c54cd310455ecc49a5c9af82fad96be66f), but the fix needs to be backmerged to 5.5 and then merged to 10.0.

Generated at Thu Feb 08 07:31:01 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.