Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-8951

main.event_1 test fails due to 2015-10-10 being insufficiently futuristic

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.0.21, 5.5, 10.0
    • Fix Version/s: 5.5.47, 10.0.22
    • Component/s: Tests
    • 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.

        Attachments

          Activity

            People

            Assignee:
            serg Sergei Golubchik
            Reporter:
            davidgow David Gow
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: