Bug #27035 information_schema test fails on MySQL 5.0.37
Submitted: 11 Mar 2007 16:53 Modified: 3 Jan 2008 15:21
Reporter: Giuseppe Maxia Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Packaging Severity:S3 (Non-critical)
Version:5.0.37 binaries OS:Linux (Linux, Mac OS X)
Assigned to: Horst Hunger CPU Architecture:Any
Tags: build, information_schema, Tests

[11 Mar 2007 16:53] Giuseppe Maxia
Description:
The information_schema test fails on Linux or Mac OS/X.

Errors are (from /opt/mysql/5.0.37/mysql-test/var/log/mysqltest-time) :
mysqltest: Result length mismatch
(the last lines may be the most important ones)
Below are the diffs between actual and expected results:
-------------------------------------------------------
*** r/information_schema.result 2007-03-02 18:13:21.000000000 +0300
--- r/information_schema.reject 2007-03-11 19:19:45.000000000 +0300
***************
*** 1096,1102 ****
  group by column_type order by num;
  column_type   group_concat(table_schema, '.', table_name)     num
  varchar(20)   information_schema.COLUMNS,information_schema.PROFILING 2
! varchar(7)    information_schema.PROFILING,information_schema.PROFILING,information_schema.PROFILING,information_schema.ROUTINES,information_schema.VIEWS      5
  create table t1(f1 char(1) not null, f2 char(9) not null)
  default character set utf8;
  select CHARACTER_MAXIMUM_LENGTH, CHARACTER_OCTET_LENGTH from
--- 1096,1102 ----
  group by column_type order by num;
  column_type   group_concat(table_schema, '.', table_name)     num
  varchar(20)   information_schema.COLUMNS,information_schema.PROFILING 2
! varchar(7)    information_schema.ROUTINES,information_schema.VIEWS    2
  create table t1(f1 char(1) not null, f2 char(9) not null)
  default character set utf8;
  select CHARACTER_MAXIMUM_LENGTH, CHARACTER_OCTET_LENGTH from

How to repeat:
1) download and install the tar.gz package for Linux or Mac OS X
2) run the test suite

$ cd $basedir/mysql-test
$ ./mysql-test-run-pl information_schema

Suggested fix:
It should be related to SHOW PROFILE implementation. 
Two columns in the PROFILING table were previously defined as VARCHAR(7). Now they are VARCHAR(9), and thus the test fails.
(Incidentally, they should use type DOUBLE. See Bug#26600)
[3 Jan 2008 15:21] Giuseppe Maxia
Fixed in 5.0.45