Bug #29705 mysql_client_test errors during tests when building MySQL from SRPM
Submitted: 11 Jul 2007 2:31 Modified: 11 Jul 2007 9:52
Reporter: Gerry Reno
Status: Duplicate
Category:Server: Tests Severity:S3 (Non-critical)
Version:5.1.20-beta OS:Linux
Assigned to: Target Version:

[11 Jul 2007 2:31] Gerry Reno 
Description:

mysql_client_test              [ fail ]

Errors are (from
/home/greno/redhat/tmp/mysql-5.1.20-beta/mysql-release-5.1.20-beta/mysql-test/var/log/mysqltest-time)
:
sh: line 1:  4890 Aborted                
/home/greno/redhat/tmp/mysql-5.1.20-beta/mysql-release-5.1.20-beta/tests/mysql_client_test
--no-defaults --testcase --user=root --port=12000 --socket=/tmp/4HHhxxvOhW/master.sock
--vardir=/home/greno/redhat/tmp/mysql-5.1.20-beta/mysql-release-5.1.20-beta/mysql-test/var
--getopt-ll-test=25600M >>
/home/greno/redhat/tmp/mysql-5.1.20-beta/mysql-release-5.1.20-beta/mysql-test/var/log/mysql_client_test.log
2>&1
mysqltest: At line 12: command "$MYSQL_CLIENT_TEST --getopt-ll-test=25600M >>
$MYSQLTEST_VARDIR/log/mysql_client_test.log 2>&1" failed
(the last lines may be the most important ones)
Result from queries before failure can be found in
/home/greno/redhat/tmp/mysql-5.1.20-beta/mysql-release-5.1.20-beta/mysql-test/var/log/mysql_client_test.log

How to repeat:
rpmbuild -ba MySQL.spec
[11 Jul 2007 2:33] Gerry Reno 
exec of
'/home/greno/redhat/tmp/mysql-5.1.20-beta/mysql-release-5.1.20-beta/tests/mysql_client_test
--no-defaults --testcase --user=root --port=12000 --socket=/tmp/4HHhxxvOhW/master.sock
--vardir=/home/greno/redhat/tmp/mysql-5.1.20-beta/mysql-release-5.1.20-beta/mysql-test/var
--getopt-ll-test=25600M >>
/home/greno/redhat/tmp/mysql-5.1.20-beta/mysql-release-5.1.20-beta/mysql-test/var/log/mysql_client_test.log
2>&1 failed, error: 34304, status: 134, errno: 0
[root@grp-01-50-50 log]#
[11 Jul 2007 3:05] Gerry Reno 
I see where there was a patch submitted to address this issue for 5.1.21-beta.  So is
there any workaround to get 5.1.20-beta to build from SRPM?
[11 Jul 2007 9:52] Sveta Smirnova 
Please do not submit the same bug more than once. An existing bug report already describes
this very problem. Even if you feel that your issue is somewhat different, the resolution
is likely
to be the same. Because of this, we hope you add your comments to the original bug
instead.

Thank you for your interest in MySQL.

Duplicate of bug #27383.

Please wait when version 5.1.21 is released.