Bug #8944 mysqldump test fails with charset utf8
Submitted: 4 Mar 2005 10:32 Modified: 4 May 2005 16:00
Reporter: noah williamsson Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1.10 OS:MacOS (Mac OS X 10.3)
Assigned to: CPU Architecture:Any

[4 Mar 2005 10:32] noah williamsson
Description:
make test fails after compiling mysql --with-charset=utf8

mysqlbinlog                    [ pass ]
mysqlbinlog2                   [ pass ]
mysqldump                      [ fail ]

Errors are (from /data/FrontA/software/mysql-4.1.10/mysql-test/var/log/mysqltest-time) :
/data/FrontA/software/mysql-4.1.10/client/.libs/mysqltest: At line 168: Result length mismatch
(the last lines may be the most important ones)
Below are the diffs between actual and expected results:
-------------------------------------------------------
*** r/mysqldump.result  Mon Feb 14 19:58:34 2005
--- r/mysqldump.reject  Fri Mar  4 13:00:51 2005
***************
*** 414,420 ****

  /*!40000 ALTER TABLE `t1` DISABLE KEYS */;
  LOCK TABLES `t1` WRITE;
! INSERT INTO `t1` VALUES ('ÄÖÜß');
  UNLOCK TABLES;
  /*!40000 ALTER TABLE `t1` ENABLE KEYS */;

--- 414,420 ----

  /*!40000 ALTER TABLE `t1` DISABLE KEYS */;
  LOCK TABLES `t1` WRITE;
! INSERT INTO `t1` VALUES ('Ã
                             ÃÃÃ');
  UNLOCK TABLES;
  /*!40000 ALTER TABLE `t1` ENABLE KEYS */;

-------------------------------------------------------
Please follow the instructions outlined at
http://www.mysql.com/doc/en/Reporting_mysqltest_bugs.html
to find the reason to this problem and how to report this.

Aborting: mysqldump failed in default mode. To continue, re-run with '--force'.

Ending Tests
Shutting-down MySQL daemon

Master shutdown finished
Slave shutdown finished
make: *** [test] Error 1

How to repeat:
# (./configure --enable-local-infile --with-comment --with-mysqlfs --with-vio --with-charset=latin1 --with-extra-charsets=all  --enable-assembler --enable-thread-safe-client --with-openssl --enable-shared --prefix=/opt/FrontA/mysql-4.1.10 --localstatedir=/data/FrontA/mysql && make all && make test )

Suggested fix:
--with-charset=latin1 works fine
[19 Mar 2005 23:00] imacat .
I have experience exactly the same issue.  My system is Linux 2.4.26.
    And my question is:  Is it safe to use the binary with this error?   Now I switch back to latin-1, but since I'm in Taiwan, latin-1 is not what I'm working with.  May I ignore this error and use the UTF-8-built binary, or should I stick with latin-1?
[4 May 2005 10:33] Hartmut Holzgraefe
verified with 4.1.10a source on MacOS X, now testing latest 4.1 source
[4 May 2005 15:54] Hartmut Holzgraefe
verified with 4.1.10 on both MacOS/X and Linux, 
works fine with 4.1.11 on Linux, so i assume it being fixed already