This might be related to Bug#347615 (https://bugs.launchpad.net/bugs/347615), but some changes to mysqltest.cc and mysql-test-run.pl have been implemented, so I am not certain. This is occurring on Mac OSX 10.5 using fresh branches of Maria from lp (bzr branch lp:maria)

What happens is that mysql-test-run aborts a test run even if --force and --max-test-fail=0 are used.

I have tried this with and without max-test-fail being set. A small number of additional test failures occur before this failure / crash, so it could be related to --extra-port crashing the server. However, it is very odd for mysql-test-run to abort a run in progress even if something untoward happens to the test server.

Sample output: (NOTE: Not all of the tests have been run at this point and some other failures have occurred prior to this, notably main.connect)

main.pool_of_threads [ fail ]
Test ended at 2009-03-24 01:00:14

CURRENT_TEST: main.connect
CURRENT_TEST: main.connect
CURRENT_TEST: main.pool_of_threads
CURRENT_TEST: main.pool_of_threads

The server [mysqld.1 - pid: 80786, winpid: 80786, exit: 0] crashed while running 'check testcase before test'

• saving '<snip>/mysql-test/var/log/main.pool_of_threads/' to '<snip>/mysql-test/var/log/main.pool_of_threads/'

Test has failed 2 times, no more retries!

mysql-test-run: *** ERROR: Test suite failure.