Bug #53284 test main.ctype_cp1251 is unsafe
Submitted: 29 Apr 2010 10:30 Modified: 27 Jul 2010 23:25
Reporter: Marc ALFF Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Tests Severity:S3 (Non-critical)
Version:mysql-next-mr OS:Any
Assigned to: CPU Architecture:Any

[29 Apr 2010 10:30] Marc ALFF 
Description:
CURRENT_TEST: main.ctype_cp1251
--- /export/home/pb2/test/sb_0-1739441-1272459053.53/mysql-5.6.99-m4-solaris10-sparc-64bit-test/mysql-test/r/ctype_cp1251.result	2010-04-28 13:24:56.000000000 +0300
+++ /export/home/pb2/test/sb_0-1739441-1272459053.53/mysql-5.6.99-m4-solaris10-sparc-64bit-test/mysql-test/r/ctype_cp1251.reject	2010-04-28 17:18:34.974681000 +0300
@@ -467,6 +467,8 @@
 ) ENGINE=MyISAM DEFAULT CHARSET=latin1
 drop table t1;
 create table t1 as select concat(rand()) as c1;
+Warnings:
+Warning	1265	Data truncated for column 'c1' at row 1
 show create table t1;
 Table	Create Table
 t1	CREATE TABLE `t1` (

mysqltest: Result content mismatch

 - saving '/export/home/pb2/test/sb_0-1739441-1272459053.53/mysql-5.6.99-m4-solaris10-sparc-64bit-test/mysql-test/var-ps_row/log/main.ctype_cp1251/' to '/export/home/pb2/test/sb_0-1739441-1272459053.53/mysql-5.6.99-m4-solaris10-sparc-64bit-test/mysql-test/var-ps_row/log/main.ctype_cp1251/'

Retrying test, attempt(2/3)...

main.ctype_cp1251                        [ retry-pass ]   6477

Retrying test, attempt(3/3)...

main.ctype_cp1251                        [ retry-pass ]   6884

How to repeat:
See PB2 logs
[27 May 2010 11:25] Sveta Smirnova 
Thank you for the report.

Please provide exact link to logs with failed tests: latest ones don't contain failure.
[27 Jun 2010 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".
[28 Jul 2010 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".