Bug #6275 "client_test" fail in 4.1.7 make test
Submitted: 27 Oct 2004 6:30 Modified: 14 Dec 2004 12:04
Reporter: Yukihiro KAWADA Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Compiling Severity:S2 (Serious)
Version:4.1.7 OS:Any (Any)
Assigned to: Alexander Barkov CPU Architecture:Any

[27 Oct 2004 6:30] Yukihiro KAWADA
make  test error
4.1.7 build
I checked on Linux(x86) or Solaris(sparc)

How to repeat:
client_test                    [ fail ]

Errors are (from /export/staff/mysql-4.1.7/mysql-test/var/log/mysqltest-time) :
client_test.c:296: check failed: 'rc == 0'
/raid/var/export/staff/mysql-4.1.7/client/mysqltest: command "$TESTS_BINDIR/client_test --testcase --user=root --socket=$MASTER_MYSOCK --port=$MYSQL_TCP_PORT" failed
(the last lines may be the most important ones)

Aborting: client_test failed. To continue, re-run with '--force'.

Ending Tests
[27 Oct 2004 6:36] Shuichi Tamagawa
I had the same error on SuSE Linux 9.0.
(Linux 2.4.21-243-default #1 Thu Aug 12 15:22:14 UTC 2004 i686)
[27 Oct 2004 7:31] Shuichi Tamagawa
It seems that this happens if configured with multi-byte character set by using --with-charset option. It passed the test after removing --with-charset=ujis from configure option.
[27 Oct 2004 8:52] Hartmut Holzgraefe
verified, reproduced with

  configure --with-charset=ujis ; make; make test

the failing statement in client_test.c and the error message are:

UPDATE myclient_test SET name= 'updated' WHERE name= 'deleted';

ERROR 1267 (HY000): Illegal mix of collations (ujis_japanese_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '='
[27 Oct 2004 8:56] Yukihiro KAWADA
configure options are:

./configure --prefix=/usr/local/mysql41 --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --enable-assembler --disable-shared --with-mysqld-ldflags=-all-static --with-charset=utf8 --with-innodb

key word is '--with-charset=utf8'
[14 Dec 2004 12:04] Alexander Barkov
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

Fixed in 4.1.8