[MDEV-3012] LP:439120 - MariaDB test suite failure (XtraDB) Created: 2009-09-30  Updated: 2012-10-04  Resolved: 2012-10-04

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Cafuego (Inactive) Assignee: Kristian Nielsen
Resolution: Fixed Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug439120.xml    

 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



 Comments   
Comment by Sergei Petrunia [ 2009-09-30 ]

Re: MariaDB test suite failure (XtraDB)
Interesting that we have this test pass in our buildbot on Jaunty:
http://askmonty.org/buildbot/builders/jaunty-amd64-rel/builds/160/steps/test/logs/stdio (check out http://askmonty.org/buildbot/builders/jaunty-amd64-rel/builds/160/ to see how buildbot does compiling and testing)

Could you please provide all commands that you you used for configuration, compilation, and test run?

Comment by Arjen Lentz (Inactive) [ 2009-09-30 ]

Re: [Ourdelta-developers] [Bug 439120] Re: MariaDB test suite failure (XtraDB)
Hi Sergey

On 30/09/2009, at 4:39 PM, Sergey Petrunia wrote:
> Interesting that we have this test pass in our buildbot on Jaunty:
> http://askmonty.org/buildbot/builders/jaunty-amd64-rel/builds/160/steps/test/logs/stdio
> (check out http://askmonty.org/buildbot/builders/jaunty-amd64-rel/builds/160/
> to see how buildbot does compiling and testing)
>
> Could you please provide all commands that you you used for
> configuration, compilation, and test run?

See https://code.launchpad.net/~cafuego/ourdelta/ourdelta-mariadb51-2-
cafuego
Builds are done with bakery/tarbake from the build-test branch and
then bakery/autobake51-deb

But do check source before delving into the build foo... I doubt the
build did something like this.

Cheers,
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: New
> Status in OurDelta - Builds for MySQL,MariaDB: Triaged
> Status in Patches for MySQL by Percona: 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@lists.launchpad.net
> 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

Comment by Kristian Nielsen [ 2009-09-30 ]

Re: MariaDB test suite failure (XtraDB)
This is also seen in the `make dist` builder in our buildbot:

https://askmonty.org/buildbot/builders/hardy-amd64-makedist/builds/5/steps/test/logs/stdio

This happens because the testsuite tries to run the test with XtraDB disabled and the innodb plugin loaded dynamically. This should not happen, as XtraDB is the only innodb we use in MariaDB (and it includes the innodb plugin).

To fix, I disabled the innodb plugin directory completely (renamed plug.in).

Fix pushed to lp:~maria-captains/maria/maria-5.1-merge

Comment by Arjen Lentz (Inactive) [ 2009-10-15 ]

Re: [Ourdelta-developers] [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@lists.launchpad.net
> 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

Comment by Rasmus Johansson (Inactive) [ 2009-10-30 ]

Launchpad bug id: 439120

Generated at Thu Feb 08 06:45:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.