database/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-08-01 03:47:19 +03:00
Code Activity

Fix the non-determinism in innodb_information_schema.test

Browse Source 
Thanks to Kristian Nielsen for finding out the root cause for the
failure, see: https://bugs.launchpad.net/maria/+bug/677407
This commit is contained in:
Vasil Dimov
2011-02-17 19:09:53 +02:00
parent 61449541fb
commit a27d85aa46
1 changed files with 23 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
mysql-test/suite/innodb_plugin/t/innodb_information_schema.test
View File

@ -116,11 +116,29 @@ SELECT * FROM ```t'\"_str` WHERE c1 = '4' FOR UPDATE;
# executes before some of them, resulting in less than expected number # executes before some of them, resulting in less than expected number
# of rows being selected from innodb_locks. If there is a bug and there # of rows being selected from innodb_locks. If there is a bug and there
# are no 14 rows in innodb_locks then this test will fail with timeout. # are no 14 rows in innodb_locks then this test will fail with timeout.
let $count = 14; # Notice that if we query INNODB_LOCKS more often than once per 0.1 sec
let $table = INFORMATION_SCHEMA.INNODB_LOCKS; # then its contents will never change because the cache from which it is
-- source include/wait_until_rows_count.inc # filled is updated only if it has not been read for 0.1 seconds. See
# the above enables the query log, re-disable it # CACHE_MIN_IDLE_TIME_US in trx/trx0i_s.c.
-- disable_query_log let $cnt=10;
while ($cnt)
{
let $success=`SELECT COUNT(*) = 14 FROM INFORMATION_SCHEMA.INNODB_LOCKS`;
if ($success)
{
let $cnt=0;
}
if (!$success)
{
real_sleep 0.2;
dec $cnt;
}
}
if (!$success)
{
-- echo Timeout waiting for rows in INNODB_LOCKS to appear
}
SELECT lock_mode, lock_type, lock_table, lock_index, lock_rec, lock_data SELECT lock_mode, lock_type, lock_table, lock_index, lock_rec, lock_data
FROM INFORMATION_SCHEMA.INNODB_LOCKS ORDER BY lock_data; FROM INFORMATION_SCHEMA.INNODB_LOCKS ORDER BY lock_data;