Bug #39280 mysql-test-run.pl always removes the mysql-test/var directory

• Submitted: 5 Sep 2008 19:18
• Modified: 19 Jun 2009 11:33
• Reporter: Omer Barnir (OCA)
• Status: Won't fix
• Category: Tools: MTR / mysql-test-run
• Severity: S3 (Non-critical)
• Version: 6.0 (all)
• OS: Any
• Assigned to: Bjørn Munch
• CPU Architecture: Any

[5 Sep 2008 19:18] Omer Barnir

Description:
mysql-test-run.pl includes a --vardir option that allows to use a 'var' directory in a location different then  the default one (mysql-test/var).

By default, mysql-test-run.pl resets the 'var' directory 

The problem is that the when starting with a --vardir=/tmp/var_foo option, mysql-testrun.pl will reset both the '/tmp/var_foo' directory but *also* the default var directory.

This prevents the ability to start a second mysql server (with a different MTR_BUILD_THREAD value) from the same directory of a system running using the default var dirrectory  

How to repeat:
start mysql-test-run.pl --start-and-exit, verify that the server has started and that the mysql-test/var directory was created.

set MTR_BUILD_THREAD to a value (so not to have a port conflict) and start mysql-test-run.pl --start-and-exit --vardir=/some/directory

>>> Observe the default mysql-test/var directory is empty

Suggested fix:
If --vardir is specified, only reset the directory referenced in it and not the default 'mysql-test/var' directory.

[19 Jun 2009 11:33] Bjørn Munch

I don't think I want to do this, it will change the external behavior.