maria-developers team mailing list archive

[Kristian Nielsen <knielsen@xxxxxxxxxxxxxxx>]

Marcin Kulisz <debian@xxxxxxxxxx> writes:

> as promised I'm attaching build log for maria DB, it's much smaller then
> anticipated.

Thanks!

> From what I can tell it was just one test which failed and rendered whole build as a
> failure.
> My build env is based on cowbuilder on fully patched SID chroot.

Ah, I see what is going on:

> plugins.unix_socket                      [ fail ]
>         Test ended at 2013-05-11 00:12:52

> --- /tmp/buildd/mariadb-5.5-5.5.29/builddir/mysql-test/suite/plugins/r/unix_socket.result	2013-05-10 21:49:20.510929790 +0000
> +++ /tmp/buildd/mariadb-5.5-5.5.29/builddir/mysql-test/suite/plugins/r/unix_socket.reject	2013-05-11 00:12:52.562350485 +0000
> @@ -8,7 +8,7 @@
>  #
>  select user(), current_user(), database();
>  user()	current_user()	database()
> -USER@localhost	USER@%	test
> +USER@localhost	USER@localhost	test
>  #
>  # name does not match = failure
>  #

Right, so the problem is that this test is poorly written. Its output depends
on the name of unix username of the account running the test!

I am guessing that in your case, you build as user root. Since the MariaDB
server running in the test happens to also have a (database) account named
root, we get an authenticated user USER@localhost instead of an anonymous
user.

I have now pushed a fix for this problem to the MariaDB tree:

    http://lists.askmonty.org/pipermail/commits/2013-May/004715.html

So this fix will appear in MariaDB 5.5.31 or possibly 5.5.32 (not sure if it
made it in 5.5.31, which I think is due for release).

Until that fix propagates to the MariaDB packaging, some options for a
work-around are:

 - Run the build as a non-root user, with fakeroot.

 - Skip the test suite during build (DEB_BUILD_OPTIONS=nocheck) (this will
   also greatly speed up the build).

 - Apply the linked patch manually

Hope this helps,

 - Kristian.