MySQL Bugs: #3474: r/timezone.reject

Bug #3474	r/timezone.reject
Submitted:	14 Apr 2004 16:33	Modified:	28 Apr 2004 13:40
Reporter:	Bob Ross	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S1 (Critical)
Version:	4.0.18	OS:	Linux (Slackware 9.1)
Assigned to:	Michael Widenius	CPU Architecture:	Any

Description:
I found this also listed once in the search, butthere was no fix listed with it.

timezone                       [ fail ]

Errors are (from /usr/local/mysql-standard-4.0.18-pc-linux-i686/mysql-test/var/log/mysqltest-time) :
/usr/local/mysql-standard-4.0.18-pc-linux-i686/bin/mysqltest: At line 48: Result length mismatch
(the last line(s) may be the ones that caused the die() in mysqltest)
Below are the diffs between actual and expected results:
-------------------------------------------------------
*** r/timezone.result   Tue Feb 10 21:39:43 2004
--- r/timezone.reject   Thu Apr 15 02:14:41 2004
***************
*** 1,7 ****
  DROP TABLE IF EXISTS t1;
  show variables like "timezone";
  Variable_name Value
! timezone      MET
  select @a:=FROM_UNIXTIME(1);
  @a:=FROM_UNIXTIME(1)
  1970-01-01 01:00:01
--- 1,7 ----
  DROP TABLE IF EXISTS t1;
  show variables like "timezone";
  Variable_name Value
! timezone      MEST
  select @a:=FROM_UNIXTIME(1);
  @a:=FROM_UNIXTIME(1)
  1970-01-01 01:00:01
-------------------------------------------------------

How to repeat:
run mysql-test-run

Suggested fix:
Unknown

I finally installed it again for the third time and I did get an error in the log file it refered me to.

/usr/local/mysql/bin/mysqltest: At line 48: Result length mismatch

Hope this helps.

Thanks
Bob Ross

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
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

This is already fixed in the current MySQL 4.0.18 tree and fix will be in 4.0.19 

Note that this is not a bug in mysql but in the test suite, so this error can be ignored.