ourdelta-developers team mailing list archive

[Yasufumi Kinoshita <yasufumi.kinoshita@xxxxxxxxxxx>]

** Also affects: percona-xtradb
   Importance: Undecided
       Status: New

** Changed in: percona-patches
       Status: New => Invalid

-- 
MariaDB test suite failure (XtraDB)
https://bugs.launchpad.net/bugs/439120
You received this bug notification because you are a member of OurDelta-
developers, which is the registrant for OurDelta.

Status in Maria: Fix Released
Status in OurDelta - Builds for MySQL,MariaDB: Fix Released
Status in Patches for MySQL by Percona: Invalid
Status in Percona XtraDB Storage Engine for MySQL: New

Bug description:
The "test-force" test suite is returning a few errors on Ubuntu Jaunty.  The first one I'd say looks like a string isn't properly initialised, the other one seems to be due to a change in the (default) innodb file format.


The first one is main.innodb-index:

--- mysql-5.1.38-maria-beta1/builddir/mysql-test/r/innodb-index.result    2009-09-30 05:16:25.000000000 +0300
+++ mysql-5.1.38-maria-beta1/builddir/mysql-test/r/innodb-index.reject    2009-09-30 05:29:38.000000000 +0300
 -1135,3 +1135,5 @@
 DROP TABLE t2;
 DROP TABLE t1;
 SET GLOBAL innodb_file_format_check=@save_innodb_file_format_check;
+Warnings:
+Warning        1210    Ignoring SET innodb_file_format=Antelope??????????3?*

mysqltest: Result length mismatch

... it looks like there is garbage in the innodb_file_format variable.


The second one is main.innodb_bug36172:

--- mysql-5.1.38-maria-beta1/builddir/mysql-test/var/tmp/check-mysqld_1.result    2009-09-30 05:31:49.000000000 +0300
+++ mysql-5.1.38-maria-beta1/builddir/mysql-test/var/tmp/check-mysqld_1.reject    2009-09-30 05:31:49.000000000 +0300
 -88,7 +88,7 @@
 INNODB_DOUBLEWRITE     ON
 INNODB_FAST_SHUTDOWN   1
 INNODB_FILE_FORMAT     Antelope
-INNODB_FILE_FORMAT_CHECK       Antelope
+INNODB_FILE_FORMAT_CHECK       Barracuda
 INNODB_FILE_IO_THREADS 4
 INNODB_FILE_PER_TABLE  OFF
 INNODB_FLUSH_LOG_AT_TRX_COMMIT 1