Kristofer Pettersson baeac87623 Bug#19027 MySQL 5.0 starts even with Fatal InnoDB errors ... Fix bug in mtr_cases.pm script visible only when InnoDB isn't configured. mysql-test/lib/mtr_cases.pm: If InnoDB isn't configured the help texts won't show the "innodb" option and mysqld_variables will not contain any "innodb" entry.		2009-05-17 22:16:21 +02:00
..
My	merge from main	2009-03-18 13:44:05 +01:00
t	Use My::Platform	2008-02-20 14:55:30 +01:00
v1	Bug#40742 MTR_VERSION=1 perl mysql-test-run.pl --start-and-exit rpl_alter does not work	2008-11-14 15:39:12 +01:00
mtr_cases.pm	Bug#19027 MySQL 5.0 starts even with Fatal InnoDB errors	2009-05-17 22:16:21 +02:00
mtr_gcov.pl	Bug#40446 - mysql-test-run --gcov is broken	2009-02-27 12:20:53 +01:00
mtr_gprof.pl	my_strtoll10-x86.s:	2006-12-31 01:02:27 +01:00
mtr_io.pl	Bug#39861:	2008-11-14 23:35:32 +03:00
mtr_match.pm	Check warnings in servers error log as part of test case	2008-04-08 16:51:26 +02:00
mtr_misc.pl	Use My::Platform	2008-02-20 14:55:30 +01:00
mtr_process.pl	WL#4189	2007-12-12 18:19:24 +01:00
mtr_report.pm	Bug #43148 MTR2 + PB2 should display correct number of failures	2009-03-09 12:59:34 +01:00
mtr_stress.pl	WL#4189	2007-12-12 18:19:24 +01:00
mtr_unique.pm	Bug #43132 Pusbbuild 2 host sol10 sparc64 max is not running tests due to port unavailble	2009-03-04 11:34:47 +01:00