| Bug #29830 | Test case 'events_scheduling' fails on Mac OS X and Windows | ||
|---|---|---|---|
| Submitted: | 16 Jul 2007 16:08 | Modified: | 21 Dec 2007 16:33 |
| Reporter: | Kent Boortz | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Tests: Server | Severity: | S3 (Non-critical) |
| Version: | 5.2.4-alpha | OS: | MacOS (PowerPC, x86) |
| Assigned to: | Damien Katz | CPU Architecture: | Any |
| Tags: | pbfail | ||
[3 Aug 2007 7:52]
Ingo Strüwing
It does also fail on Windows: See push Thu Aug 2 19:18:41 2007 istruewing, platform 'vm-win2003-32-a' Win32 VS2003 -max-nt, https://intranet.mysql.com/secure/pushbuild/showdir.pl?dir=mysql-5.1-engines main.events_scheduling [ fail ] Errors are (from e:/var-ps_row-101/log/mysqltest-time) : mysqltest: Result length mismatch (the last lines may be the most important ones) Below are the diffs between actual and expected results: ------------------------------------------------------- *** C:/cygwin/home/pushbuild/pb1/pb/mysql-5.1-engines/228/mysql-5.1.21-beta-pb228/mysql-test/r/events_scheduling.result Thu Aug 2 20:33:27 2007 --- C:/cygwin/home/pushbuild/pb1/pb/mysql-5.1-engines/228/mysql-5.1.21-beta-pb228/mysql-test/r/events_scheduling.reject Thu Aug 2 21:33:31 2007 *************** *** 82,88 **** FROM INFORMATION_SCHEMA.EVENTS WHERE EVENT_SCHEMA=DATABASE() AND EVENT_NAME='event_2'; IF(LAST_EXECUTED-ENDS < 3, 'OK', 'ERROR') ! OK "Already dropped because ended. Therefore an error." DROP EVENT event_3; ERROR HY000: Unknown event 'event_3' --- 82,88 ---- FROM INFORMATION_SCHEMA.EVENTS WHERE EVENT_SCHEMA=DATABASE() AND EVENT_NAME='event_2'; IF(LAST_EXECUTED-ENDS < 3, 'OK', 'ERROR') ! ERROR "Already dropped because ended. Therefore an error." DROP EVENT event_3; ERROR HY000: Unknown event 'event_3' ------------------------------------------------------- Please follow the instructions outlined at
[23 Nov 2007 16:02]
Ingo Strüwing
This bug makes the test suite fail randomly. Raising the priority so that it can be fixed. See pushbuild, for example https://intranet.mysql.com/secure/pushbuild/showdir.pl?dir=mysql-5.1-engines log https://intranet.mysql.com/secure/pushbuild/getlog.pl?dir=mysql-5.1-engines&entry=rkalimul...
[23 Nov 2007 16:03]
Ingo Strüwing
Disabling the test case. Please re-enable after fix.
[28 Nov 2007 10:24]
Bugs System
Pushed into 6.0.4-alpha
[28 Nov 2007 10:26]
Bugs System
Pushed into 5.1.23-rc
[7 Dec 2007 21:01]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/39574 ChangeSet@1.2654, 2007-12-07 16:00:50-05:00, dkatz@damien-katzs-computer.local +3 -0 Bug#29830 Test case 'events_scheduling' fails on Mac OS X and Windows. Changed LAST_EXECUTED time the event execution start time, instead of the execution completion time.
[8 Dec 2007 0:28]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/39588 ChangeSet@1.2678, 2007-12-07 19:27:45-05:00, dkatz@damien-katzs-computer.local +4 -0 Bug#29830 Test case 'events_scheduling' fails on Mac OS X and Windows. Change LAST_EXECUTED time the execution start time, instead of the execution completion time. This ensures the END time always the same or later than the LAST_EXECUTED time.
[11 Dec 2007 1:00]
Damien Katz
Pushed to 5.1-engines.
[12 Dec 2007 23:00]
Bugs System
Pushed into 6.0.5-alpha
[12 Dec 2007 23:02]
Bugs System
Pushed into 5.1.23-rc
[21 Dec 2007 16:33]
Paul DuBois
Noted in 5.1.23, 6.0.5 changelogs. The LAST_EXECUTED column of the INFORMATION_SCHEMA.EVENTS table now indicates when the event started executing rather than when it finished executing. As a result, the ENDS column is never less than LAST_EXECUTED. Also updated section for INFORMATION_SCHEMA.EVENTS table.
Description: Test case 'events_scheduling' fails on Mac OS X with ------------------------------------------------------- *** r/events_scheduling.result --- r/events_scheduling.reject *************** *** 90,95 --- 90,98 "Should be preserved" SELECT EVENT_NAME, STATUS FROM INFORMATION_SCHEMA.EVENTS ORDER BY EVENT_NAME; EVENT_NAME STATUS + abc1 ENABLED + abc2 ENABLED + abc3 ENABLED event_2 DISABLED event_4 DISABLED DROP EVENT event_2; ------------------------------------------------------- How to repeat: Run the test case on the specified platform