Bug #19087 events_scheduling.test fails in 5.1-bk
Submitted: 13 Apr 2006 19:46 Modified: 13 Apr 2006 20:02
Reporter: Sergey Petrunya Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Stored Routines Severity:S3 (Non-critical)
Version:5.1-bk OS:Linux (Linux x86)
Assigned to: CPU Architecture:Any

[13 Apr 2006 19:46] Sergey Petrunya
Description:
events_scheduling.test fails in current 5.2 in the following way: 

events_scheduling              [ fail ]

Errors are (from /data/users/spetrunia/mysql-5.1-apr13-test-3/mysql-test/var/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:
-------------------------------------------------------
*** r/events_scheduling.result  2006-04-13 21:21:17.204578914 +0300
--- r/events_scheduling.reject  2006-04-13 21:47:04.005294976 +0300
***************
*** 31,37 ****
  OK
  SELECT IF(LAST_EXECUTED-ENDS < 2, 'OK', 'ERROR') FROM INFORMATION_SCHEMA.EVENTS WHERE EVENT_SCHEMA=DATABASE() AND EVENT_NAME='start_n_end' AND ENDS IS NOT NULL;
  IF(LAST_EXECUTED-ENDS < 2, 'OK', 'ERROR')
! OK
  DROP EVENT start_n_end;
  "Already dropped because ended. Therefore an error."
  DROP EVENT only_one_time;
--- 31,37 ----
  OK
  SELECT IF(LAST_EXECUTED-ENDS < 2, 'OK', 'ERROR') FROM INFORMATION_SCHEMA.EVENTS WHERE EVENT_SCHEMA=DATABASE() AND EVENT_NAME='start_n_end' AND ENDS IS NOT NULL;
  IF(LAST_EXECUTED-ENDS < 2, 'OK', 'ERROR')
! ERROR
  DROP EVENT start_n_end;
  "Already dropped because ended. Therefore an error."
  DROP EVENT only_one_time;
-------------------------------------------------------
Please follow the instructions outlined at
http://www.mysql.com/doc/en/Reporting_mysqltest_bugs.html
to find the reason to this problem and how to report this.

Result from queries before failure can be found in r/events_scheduling.log

Killing Possible Leftover Processes
Restoring snapshot of databases
Resuming Tests

How to repeat:
get 5.1, compile with compile-pentium-debug-max, run the mysql-test-run.pl --force.

I had this with the tip cset: 
ChangeSet@1.2337.1.1, 2006-04-13 19:02:49+03:00, aelkin@mysql.com
  Bug#19074:    rpl_row_func003 test failed
  disabled for now.
[13 Apr 2006 20:02] Andrey Hristov
Dupe of #18958