**Reported in Launchpad by Baron Schwartz last update 26-10-2012 17:50:00

The environment is supposedly OK:

[baron@localhost ~]$ 2.0/sandbox/test-env checkconfig
PERCONA_TOOLKIT_BRANCH=2.0/ - ok
PERCONA_TOOLKIT_SANDBOX=5.5.20/ - ok
Percona Toolkit test environment config is ok!

But,

[baron@localhost ~]$ 2.0/sandbox/test-env start
Invalid PERCONA_TOOLKIT_BRANCH directory: 2.0/
There was an error starting the Percona Toolkit test environment.

This is because:

if [ ! -d "$PERCONA_TOOLKIT_BRANCH" ]; then
die "Invalid PERCONA_TOOLKIT_BRANCH directory: $PERCONA_TOOLKIT_BRANCH"
fi

That's executed with a different cwd. Something is doing a "cd" to 2.0/sandbox and then executing the script. We almost surely shouldn't do that, because if we do, then it forces everyone to use absolute paths, which is never the expected behavior.

The workaround right now is to set the environment variables to absolute paths.