Description:
Test parts.partition_alter1_<eng> is failing on Windows.
For some reason, the diff results do not show a visible difference between expected and
actual test results.
Suspect that it is a quirk in interpretation of the .result files
Example output:
@@ -383,16 +383,16 @@
22738: WHERE f_int1 BETWEEN @max_row_div2 AND @max_row;
22739: # Start usability test (inc/partition_check.inc)
22740: create_command
22741: -SHOW CREATE TABLE t1;
22742: -Table Create Table
22743: -t1 CREATE TABLE `t1` (
22744: - `f_int1` int(11) NOT NULL DEFAULT '0',
22745: - `f_int2` int(11) NOT NULL DEFAULT '0',
22746: - `f_char1` char(20) DEFAULT NULL,
22747: - `f_char2` char(20) DEFAULT NULL,
22748: - `f_charbig` varchar(1000) DEFAULT NULL,
22749: - PRIMARY KEY (`f_int1`,`f_int2`)
22750: -) ENGINE=InnoDB DEFAULT CHARSET=latin1 /*!50100 PARTITION BY HASH (f_int1)
PARTITIONS 2 */
22751: +SHOW CREATE TABLE t1;
22752: +Table Create Table
22753: +t1 CREATE TABLE `t1` (
22754: + `f_int1` int(11) NOT NULL DEFAULT '0',
22755: + `f_int2` int(11) NOT NULL DEFAULT '0',
22756: + `f_char1` char(20) DEFAULT NULL,
22757: + `f_char2` char(20) DEFAULT NULL,
22758: + `f_charbig` varchar(1000) DEFAULT NULL,
22759: + PRIMARY KEY (`f_int1`,`f_int2`)
22760: +) ENGINE=InnoDB DEFAULT CHARSET=latin1 /*!50100 PARTITION BY HASH (f_int1)
PARTITIONS 2 */
How to repeat:
Run the test on a Windows machine.
From the mysql-test directory, execute the following command:
./mysql-test-run.pl --suite=parts partition_alter1_myisam
You will see similar test failures.
Suggested fix:
Need to determine what is causing the perceived difference in results (expected vs.
actual).
Will disable the offending subtests in the meantime to maintain some test functionality
while the problem is being addressed.
