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: | |
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 .
[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