Bug #37635 Test read_many_rows_innodb is failing w/ wrong error message (lock_wait_timeout)

Description:
When running mysql-test-run --force --big the following test fails:

main.concurrent_innodb main.read_many_rows_innodb main.variables-big rpl.rpl_truncate_7ndb_2 rpl.rpl_truncate_7ndb_2 rpl.rpl_truncate_7ndb_2

How to repeat:
mysql-test-run --force --big

Suggested fix:
Run --big test as part of pushbuild

Thank you for the report.

Verified as described.

main.read_many_rows_innodb main.variables-big fail in 6.0 as well

Bug #37741 was marked as duplicate of this one.

Wrote Bug #38811	Test main.variables-big failing (all versions)

This test is failing for a separate reason than the other tests listed in this bug and is a quick fix.  Breaking this fix out in order to repair a bit quickly rather than push a number of disparate fixes (that could take longer to sort out)

Wrote Bug #38903	Test rpl.rpl_truncate_7ndb_2 failing
for this failure.  This is a quick fix as well.

The read_many_rows failure will remain to be fixed on this bug.  Still investigating the cause of this failure - The test is supposed to fail due to deadlock, but instead is failing due to wait timeout.

Renaming this bug from "Some big tests fails in 5.1" as the other tests have been corrected.

The problem with read_many_rows_innodb is that it is hitting lock_wait_timeout rather than detecting the deadlock as expected.  A number of other tests are running into similar issues and this could be indicative of a larger problem:

Bug #38070	rpl_locktrans_innodb Lock wait timeout exceeded At line 632
Bug #37775	main.locktrans_innodb fails randomly
Bug #29828	Test 'rpl_locktrans_innodb' failed on HP-UX 11.11 32 bit

Failure example is listed below.  This is deterministic, the failure is the same for every run I have tried on both Windows and Mac OSX (10.5)

main.read_many_rows_innodb     [ fail ]

mysqltest: In included file "./include/read_many_rows.inc": At line 116: query 'reap' failed with wrong errno 1205: 'Lock wait timeout exceeded; try restarting transaction', instead of 1213...

The result from queries just before the failure was:
< snip >
DECLARE CONTINUE HANDLER FOR SQLSTATE '40001' SET @b:= 'deadlock';
DECLARE CONTINUE HANDLER FOR SQLEXCEPTION SET @a:= 'exception';
INSERT INTO t2 (f2) VALUES (1);
DELETE FROM t2 WHERE f2 = 1;
END;|
create procedure proc24989_2()
deterministic
begin
declare continue handler for sqlexception
select 'Outer handler' as 'exception';
insert into t1 values(1);
select "continued";
end|
start transaction;
insert into t1 values(1);
start transaction;
insert into t2 values(123);
insert into t1 values(1);
insert into t1 values(1);
ERROR HY000: Lock wait timeout exceeded; try restarting transaction

The test has been removed in 8.0.13.