MySQL Bugs: #28310: Server reports events which never were created

Bug #28310	Server reports events which never were created
Submitted:	8 May 2007 17:25	Modified:	2 Jun 2007 13:08
Reporter:	Joerg Bruehe	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Stored Routines	Severity:	S2 (Serious)
Version:		OS:	Any (varying)
Assigned to:	Andrey Hristov	CPU Architecture:	Any

Description:
This has not been observed before 5.1.18,
but it may be older (it ust happens very rarely):

-------------------------------------------------------
*** 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;
-------------------------------------------------------

The test case does not have any "abc*" events, so where do they come from ?

In one test build it happened in 
   osx-tiger-ppc-5.1-community.log,
in another one in 
   rhas3-x86-glibc23-5.1-community.log

How to repeat:
Run it sufficiently often ...

Joerg, these events are created in the preceeding test and dropped at the end of the test.
I need instructions how to reproduce this bug.

It happened while running the test suite during release builds
on the hosts listed, in 5.1.19-beta again (until now) on
  OS X on PPC (32 bit)

Andrey, assigning for your consideration.

Possible fix in 5.1-runtime
Test change, no need of review.

Possible fix in 5.1-runtime
Test change, no need of review.

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/27556

ChangeSet@1.2521, 2007-05-29 12:44:44+02:00, andrey@whirlpool.mysql.com +2 -0
  Fix for bug #28310 Server reports events which never were created
  
  Fix a race
  
  Wait at the end of the test for all events to finish.
  Then continue to the next result. This should be done, as the
  server won't be restarted, and although events are dropped with
  drop database, they could still be executing in memory.

Pushed into 5.1.20-beta

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

Test only, no end user changes to document - closed w/o further action.