Bug #7909 'client_test' fails: $TESTS_BINDIR/client_test not found
Submitted: 14 Jan 2005 15:55 Modified: 10 Feb 2005 17:31
Reporter: Joerg Bruehe Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.3-pre OS:Any (All)
Assigned to: Joerg Bruehe CPU Architecture:Any

[14 Jan 2005 15:55] Joerg Bruehe
Description:
On all platforms where the current (Jan 13) 5.0.3 could be built, Test 'client_test' failed. The symptom is:

client_test                    [ fail ]

Errors are (from /home/mysqldev/aix52/test/mysql-standard-5.0.3-alpha-ibm-aix5.2.0.0-powerpc/mysql-test/var/log/mysqltest-time) :
sh: /home/mysqldev/aix52/test/mysql-standard-5.0.3-alpha-ibm-aix5.2.0.0-powerpc/bin/client_test:  not found.
/home/mysqldev/aix52/test/mysql-standard-5.0.3-alpha-ibm-aix5.2.0.0-powerpc/bin/mysqltest: command "$TESTS_BINDIR/client_test --no-defaults --testcase --user=root --socket=$MASTER_MYSOCK --port=$MYSQL_TCP_PORT --silent" failed
(the last lines may be the most important ones)

Checking the log, I found no '.../bin/client_test' listed but a '.../tests/client_test'.
It seems the problem might be caused by this change of Jan 5:
mysql-test/mysql-test-run.sh@1.220, 2005-01-04 08:15:30+01:00, joreland@mysql.com
  Use correct path to clist_tests in on installed system

- mysql-test/mysql-test-run.sh version 1.219
+ mysql-test/mysql-test-run.sh version 1.220

@@ -537,7 +537,7 @@
 monty    1.146.1.4    |    MYSQLD="$VALGRIND $BASEDIR/bin/mysqld"
 monty    1.145        |  fi
 monty    1.146.1.45   |  CLIENT_BINDIR="$BASEDIR/bin"
-mwagner  1.208.1.12   |  TESTS_BINDIR="$BASEDIR/tests"
+joreland 1.220        |  TESTS_BINDIR="$BASEDIR/bin"
 monty    1.146.1.45   |  MYSQL_TEST="$CLIENT_BINDIR/mysqltest"
 monty    1.146.1.45   |  MYSQL_DUMP="$CLIENT_BINDIR/mysqldump"
 monty    1.146.1.45   |  MYSQL_BINLOG="$CLIENT_BINDIR/mysqlbinlog"

How to repeat:
Use the standard build + test procedure for the platforms.

Suggested fix:
Agree on a tree structure that cares for all test programs.
[17 Jan 2005 8:36] Joerg Bruehe
A changeset was committed, accepted, and pushed, needs to be checked in both a 'release build' and an 'install' situation.
[10 Feb 2005 17:31] Joerg Bruehe
Considering that the test program name was changed in the meantime, there is no use in keeping this open.