5.5.13 perfschema.global_read_lock fails when thread-handling is set to pool-of-threads

[Valentine Gostev]

tests passes fine when one thread per connection is used

perfschema.global_read_lock [ fail ]
        Test ended at 2011-05-11 14:51:04

CURRENT_TEST: perfschema.global_read_lock
--- /root/HEAP/mysql-test/suite/perfschema/r/global_read_lock.result 2011-05-06 18:25:36.760325000 +0300
+++ /root/HEAP/mysql-test/suite/perfschema/r/global_read_lock.reject 2011-05-11 13:51:04.648861662 +0300
@@ -18,13 +18,13 @@
 unlock tables;
 lock tables performance_schema.setup_instruments write;
 connection default;
+Timeout in wait_condition.inc for select 1 from performance_schema.events_waits_current where event_name like "wait/synch/cond/sql/MDL_context::COND_wait_status"
 select event_name,
 left(source, locate(":", source)) as short_source,
 timer_end, timer_wait, operation
 from performance_schema.events_waits_current
 where event_name like "wait/synch/cond/sql/MDL_context::COND_wait_status";
 event_name short_source timer_end timer_wait operation
-wait/synch/cond/sql/MDL_context::COND_wait_status mdl.cc: NULL NULL timed_wait
 unlock tables;
 update performance_schema.setup_instruments set enabled='NO';
 update performance_schema.setup_instruments set enabled='YES';

mysqltest: Result content mismatch

[Laurynas Biveinis (laurynas-biveinis)]

Perfschema bugs will be fixed later if at all.