| Bug #98107 | main.events_bugs fails in 2020 | ||
|---|---|---|---|
| Submitted: | 2 Jan 2020 8:59 | Modified: | 3 Jan 2020 13:47 |
| Reporter: | Erlend Dahl | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Tests | Severity: | S7 (Test Cases) |
| Version: | 5.6+ | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[2 Jan 2020 13:26]
Erlend Dahl
Bug#98104 events_bugs mtr failed in 2020s was marked as a duplicate.
[3 Jan 2020 13:47]
Paul DuBois
Posted by developer: Fixed in 5.6.48, 5.7.30, 8.0.20. Work was done for test suite. No changelog entry needed.
[9 Jan 2020 13:57]
Erlend Dahl
Bug#98152 mtr test failed for main.events_bugs was marked as a duplicate.
[13 Feb 2020 5:36]
MySQL Verification Team
Bug #98562 marked as duplicate of this one
Description: [ 29%] main.events_bugs w15 [ fail ] Test ended at 2020-01-02 07:43:59 CURRENT_TEST: main.events_bugs mysqltest: At line 1064: Query 'ALTER EVENT e1 COMMENT 'comment'' failed. ERROR 1539 (HY000): Unknown event 'e1' The result from queries just before the failure was: # Connection: u1_con (mysqltest_u1@localhost/events_test). # CREATE EVENT e1 ON SCHEDULE AT '2020-01-01 00:00:00' DO SET @a = 1; ERROR HY000: The MySQL server is running with the --read-only option so it cannot execute this statement ALTER EVENT e1 COMMENT 'comment'; ERROR HY000: The MySQL server is running with the --read-only option so it cannot execute this statement DROP EVENT e1; ERROR HY000: The MySQL server is running with the --read-only option so it cannot execute this statement # # Connection: root_con (root@localhost/events_test). # CREATE EVENT e1 ON SCHEDULE AT '2020-01-01 00:00:00' DO SET @a = 1; Warnings: Note 1588 Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation. How to repeat: ./mtr --mem main.events_bugs Suggested fix: Change 2020 to a later year as a stop-gap fix.