Bug #51109 configure --with-charset=utf8 --with-collation=utf8_general_ci let tests fail.
Submitted: 11 Feb 2010 15:41 Modified: 11 Feb 2010 17:09
Reporter: Horst Hunger Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Information schema Severity:S3 (Non-critical)
Version:5.5.99-m3-debug OS:Linux (suse-linux-gnu on x86_64)
Assigned to: CPU Architecture:Any

[11 Feb 2010 15:41] Horst Hunger
Description:
Testsuite failures due to character sets:
./configure ...  --with-charset=utf8 --with-collation=utf8_general_ci ...
Breaks: main.mysql_client_test main.mysql_comments main.mysql_upgrade
main.information_schema funcs_1.is_columns_mysql funcs_1.is_tables_mysql
funcs_1.is_triggers

Not all entries in information_schema will be updated if the character_set_server will be changed. They stay on the values set by configure, e.g. in information_schema where data_type= 'varchar'.
The select below shows all data_types except varchar as they have an octet_length of 3 bytes.

How to repeat:
./configure ...  --with-charset=utf8 --with-collation=utf8_general_ci ...
and run the regression and funcs_1 tests.

or run after the configuration with utf8

./mtr --start-dirty --mysqld=--character-set-server=latin1 --mysqld=--collation-server=latin1_swedish_ci alias

and in another terminal

../client/mysql --socket=var/tmp/mysqld.1.sock --user=root                                                                                         
mysql> set names latin1;
mysql> show variables like '%character%';
mysql> SELECT DISTINCT CHARACTER_OCTET_LENGTH / CHARACTER_MAXIMUM_LENGTH AS COL_CML, DATA_TYPE, CHARACTER_SET_NAME, COLLATION_NAME FROM information_schema.columns WHERE table_schema = 'mysql' ANDCHARACTER_OCTET_LENGTH / CHARACTER_MAXIMUM_LENGTH = 1 ORDER BY CHARACTER_SET_NAME, COLLATION_NAME, COL_CML;
[11 Feb 2010 17:09] Sveta Smirnova
Thank you for the report.

This is really duplicate of bug #50825