ourdelta-developers team mailing list archive
-
ourdelta-developers team
-
Mailing list archive
-
Message #00369
Re: [Bug 439120] Re: MariaDB test suite failure (XtraDB)
Hi Yasufumi, all
On 15/10/2009, at 6:27 PM, Yasufumi Kinoshita wrote:
> ** Also affects: percona-xtradb
> Importance: Undecided
> Status: New
>
> ** Changed in: percona-patches
> Status: New => Invalid
To clarify and for the record in case others encounter it - this issue
shows up depending on the configure options used.
One needs to make absolutely sure that the old plugin is disabled,
otherwise this kind of funny stuff happens.
Regards,
Arjen.
> --
> 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
>
> _______________________________________________
> Mailing list: https://launchpad.net/~ourdelta-developers
> Post to : ourdelta-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ourdelta-developers
> More help : https://help.launchpad.net/ListHelp
--
Arjen Lentz, Exec.Director @ Open Query (http://openquery.com)
Exceptional Services for MySQL at a fixed budget.
Follow our blog at http://openquery.com/blog/
OurDelta: enhanced builds for MySQL @ http://ourdelta.org
--
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
References