Bug #28416 compress test case fails
Submitted: 14 May 2007 15:04 Modified: 23 Aug 2007 7:51
Reporter: BJ Dierkes Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Tests Severity:S3 (Non-critical)
Version:5.0.41 OS:Linux (Rhel 3 x86_64)
Assigned to: Assigned Account CPU Architecture:Any
Tags: Contribution

[14 May 2007 15:04] BJ Dierkes 
Description:
The 'compress' test case seems to fail with a 'timeout' only when running the entire MySQL test suite.  When running just the 'compress' test alone, it passes without issue.

How to repeat:
./configure && make && make test

Suggested fix:
Adding 'FLUSH PRIVILEGES;' before the tests runs seems to fix the issue (at least in my case).  The following is a suggested patch:

--- mysql-5.0.41/mysql-test/t/compress.test.timeout     2007-05-14 08:06:19.000000000 -0500
+++ mysql-5.0.41/mysql-test/t/compress.test     2007-05-14 08:08:19.000000000 -0500
@@ -8,6 +8,9 @@

 connect (comp_con,localhost,root,,,,,COMPRESS);

+# Redhat build fix
+FLUSH PRIVILEGES;
+
 # Check compression turned on
 SHOW STATUS LIKE 'Compression';

--- mysql-5.0.41/mysql-test/r/compress.result.timeout   2007-05-14 08:09:52.000000000 -0500
+++ mysql-5.0.41/mysql-test/r/compress.result   2007-05-14 08:09:00.000000000 -0500
@@ -1,3 +1,4 @@
+FLUSH PRIVILEGES;
 SHOW STATUS LIKE 'Compression';
 Variable_name  Value
 Compression    ON
[20 Jun 2007 10:32] Sveta Smirnova 
Thank you for the report.

I can not repeat described issue in own environment. Please upload log files and indicate accurate version of package with which this test is broken (file name if you downladed the package from dev.mysql.com site).
[20 Jul 2007 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[23 Jul 2007 7:51] Sveta Smirnova 
Feedback is still needed.
[23 Aug 2007 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".