Bug #33104 make test Failed mysqlcheck (t_bug25347?)
Submitted: 10 Dec 2007 5:34 Modified: 13 Dec 2007 19:36
Reporter: imacat . (Basic Quality Contributor) Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: Tests Severity:S7 (Test Cases)
Version:5.0.51 OS:Linux (2.6.22.10 (Debian 4.0 r1))
Assigned to: CPU Architecture:Any

[10 Dec 2007 5:34] imacat .
Description:
    Hi.  This is imacat from Taiwan.  I have downloaded and compiled the newly-released MySQL 5.0.51.  But make test fails at mysqlcheck.  I have searched the bug database and did not found anyone reporting this before.  Please tell me if I missed something.

    The make test log is attached below.  My build environement is Debian GNU/Linux 4.0r1, Linux kernel 2.6.22.10, gcc 4.1.2, glibc 2.3.6.  Both i386 and x86_64 fails.  My build configuration is:

./configure --quiet --prefix=/usr --sysconfdir=/etc --localstatedir=/var/lib/mysql --infodir=/usr/share/info --mandir=/usr/share/man --enable-thread-safe-client --enable-assembler --with-extra-charsets=all --with-unix-socket-path=/var/run/mysql/mysql.sock --with-mysqld-user=mysql --without-bench --without-readline

    Hope that this helps.  Please tell me if you need any more information.  Thank you.

=================
imacat@atlas src/mysql-5.0.51 % make test
Logging: ./mysql-test-run.pl
MySQL Version 5.0.51
Skipping ndbcluster, mysqld not compiled with ndbcluster
Skipping SSL, mysqld not compiled with SSL
Using MTR_BUILD_THREAD      = 0
Using MASTER_MYPORT         = 9306
Using MASTER_MYPORT1        = 9307
Using SLAVE_MYPORT          = 9308
Using SLAVE_MYPORT1         = 9309
Using SLAVE_MYPORT2         = 9310
Using IM_PORT               = 9312
Using IM_MYSQLD1_PORT       = 9313
Using IM_MYSQLD2_PORT       = 9314
Killing Possible Leftover Processes
Removing Stale Files
Creating Directories
Installing Master Database
Installing Slave1 Database
=======================================================
Starting Tests in the 'main' suite

TEST                           RESULT         TIME (ms)
-------------------------------------------------------

alias                          [ pass ]             19
...
mysqlbinlog2                   [ pass ]            528
mysqlcheck                     [ fail ]

--- /usr/local/src/mysql-5.0.51/mysql-test/r/mysqlcheck.result  2007-11-15 17:28:37.000000000 +0300
+++ /usr/local/src/mysql-5.0.51/mysql-test/var/log/mysqlcheck.reject    2007-12-10 07:43:52.000000000 +0300
@@ -49,7 +49,8 @@
 flush tables;
 removing and creating
 d_bug25347.t_bug25347
-error    : Incorrect file format 't_bug25347'
+Error    : Incorrect file format 't_bug25347'
+error    : Corrupt
 insert into t_bug25347 values (4),(5),(6);
 ERROR HY000: Incorrect file format 't_bug25347'
 d_bug25347.t_bug25347

mysqltest: Result content mismatch

Aborting: mysqlcheck failed in default mode.
To continue, re-run with '--force'.
Stopping All Servers
make: *** [test-ns] Error 1
imacat@atlas src/mysql-5.0.51 %

How to repeat:
% ./configure --quiet --prefix=/usr --sysconfdir=/etc --localstatedir=/var/lib/mysql --infodir=/usr/share/info --mandir=/usr/share/man --enable-thread-safe-client --enable-assembler --with-extra-charsets=all --with-unix-socket-path=/var/run/mysql/mysql.sock --with-mysqld-user=mysql --without-bench --without-readline
% make
% make test
[10 Dec 2007 16:38] David Tonhofer
I have the same problem on RH ES 4.0

This does not seem to be an actual bug, but a non-updated "check against" file.

Tests expect the following from "$INSTALLDIR/mysql-test/r/mysqlcheck.result":

-------------------------------------------------
flush tables;
removing and creating
d_bug25347.t_bug25347
error    : Incorrect file format 't_bug25347'
insert into t_bug25347 values (4),(5),(6);
ERROR HY000: Incorrect file format 't_bug25347'
d_bug25347.t_bug25347
-------------------------------------------------

but this is delivered (seems to contain an additional details line)

-------------------------------------------------
flush tables;
removing and creating
d_bug25347.t_bug25347
Error    : Incorrect file format 't_bug25347'
error    : Corrupt
insert into t_bug25347 values (4),(5),(6);
ERROR HY000: Incorrect file format 't_bug25347'
d_bug25347.t_bug25347
-------------------------------------------------

Will now test with an updated "shall-output"
[11 Dec 2007 10:46] MySQL Verification Team
Thank you for the bug report. I wasn't able to repeat with current source:

=======================================================
Starting Tests in the 'main' suite

TEST                           RESULT         TIME (ms)
-------------------------------------------------------

mysqlcheck                     [ pass ]           2572
-------------------------------------------------------
Stopping All Servers
skipped 9 bytes from file: socket (3)
[11 Dec 2007 10:47] Norbert Tretkowski
This issue is already fixed in 5.0.52, but it affects 5.0.51.
[11 Dec 2007 16:37] BJ Dierkes
Can we get official clarification of whether the bug is actually in 'mysqlcheck' or just in the test cases for 'mysqlcheck'?  

Thank you.
[11 Dec 2007 17:33] imacat .
> This issue is already fixed in 5.0.52, but it affects 5.0.51.

I see.  Will there an official 5.0.52 release?  Or is there any patch to the 5.0.51 source that fixes this bug?  I would like to run the newly-released MySQL rather than waiting for the next release announcement for several months.
[12 Dec 2007 11:56] Lenz Grimmer
This bug seems to be a duplicate of Bug#32458
[13 Dec 2007 19:36] imacat .
> This bug seems to be a duplicate of Bug#32458

Indeed.  The patch to Bug#32458 does solve my problem.  Sorry for the duplicated report, though I cannot figure out why my search on MySQL bug database with the keyword "mysqlcheck" did not find Bug#32458 in the beginning.