Bug #32172 information_schema test fails with wait_condition timeout

Description:
It seems that a wait condition timeout of 30 seconds is too short in the information_schema test.  On a loaded box (at least vm-win2003-32-a) the
test times out, causing test failure:

main.information_schema        [ fail ]

--- C:/cygwin/home/pushbuild/pb1/pb/mysql-6.0-opt/21/mysql-6.0.4-alpha-pb21/mysql-test/r/information_schema.result	2007-11-07 17:10:02.000000000 +0300
+++ C:\cygwin\home\pushbuild\pb1\pb\mysql-6.0-opt\21\mysql-6.0.4-alpha-pb21\mysql-test\r\information_schema.reject	2007-11-07 18:16:13.546875000 +0300
@@ -1502,6 +1502,7 @@
 WHERE variable_name LIKE 'ABORTED_CONNECTS' OR
 variable_name LIKE 'BINLOG_CACHE_DISK_USE';
 END$$
+Timeout in wait_condition.inc for select count(*) = 0 from information_schema.events where event_name='event_status'
 SELECT variable_name FROM server_status;
 variable_name
 ABORTED_CONNECTS

How to repeat:
https://intranet.mysql.com/secure/pushbuild/xref.pl?startdate=&enddate=&dir=&plat=&testtyp...

Suggested fix:
Perhaps let $wait_timeout = 60.

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

ChangeSet@1.2609, 2007-11-12 17:26:32+03:00, anozdrin@station. +1 -0
  A patch for BUG#32172: information_schema test fails with
  wait_condition timeout.
  
  The problem was that the event thread didn't manage to execute
  the event in 30 seconds on highly-loaded box. The fix is to
  increase timeout.
  
  This is a fix for the test suite.

Pushed into 5.1-rt.

Pushed into 5.1.23-rc

Pushed into 6.0.5-alpha

Change to test case. No changelog entry needed.