[MDEV-3678] LP:471160 - Ubuntu MariaDB package: can't run mysql-test-run.pl Created: 2009-11-02  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 Priority: Major
Reporter: Hakan Küçükyılmaz (Inactive) Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug471160.xml    

 Description   

On Ubuntu 9.04 32-bit and 64-bit one cannot run mysql-test-run.pl

How to repeat:
aptitude install mariadb-server mariadb-test

cd /usr/share/mysql/mysql-test
./mysql-test-run.pl
Logging: ./mysql-test-run.pl
mysql-test-run: *** ERROR: Could not find any of /usr/share/client_release /usr/share/client_debug /usr/share/client /usr/share/bin

 Comments   
Comment by Kristian Nielsen [ 2009-11-05 ]

Re: Ubuntu MariaDB package: can't run mysql-test-run.pl
Ok, I fixed in 5.1-release maria branch that mysql-test-run.pl can find the files it needs when installed in /usr/share/mysql/mysql-test/.

However, the test suite still does not run (testedUbuntu Jaunty i386).

The problem is that the apparmor profile forbids /usr/sbin/mysqld to write the files it needs to run the test suite!

This needs to be fixed somehow in the OurDelta stuff.

Comment by Hakan Küçükyılmaz (Inactive) [ 2009-11-27 ]

Re: Ubuntu MariaDB package: can't run mysql-test-run.pl
The apparmor problem still exists.

Comment by Arjen Lentz (Inactive) [ 2009-12-03 ]

Re: Ubuntu MariaDB package: can't run mysql-test-run.pl
I don't see any ref to a patch or branch or release... so, what happened, and how was it fixed and when/where?

Comment by Rasmus Johansson (Inactive) [ 2009-12-03 ]

Launchpad bug id: 471160

Comment by Kristian Nielsen [ 2009-12-03 ]

Re: Ubuntu MariaDB package: can't run mysql-test-run.pl
I fixed in MariaDB 5.1.39 that mysql-test-run.pl can run the testsuite from the location it is installed in the Ourdelta .debs (/usr/share/mysql/mysql-test/ I think).

The default work dir for the test suite is mysql-test/var, so if /usr/share/mysql/mysql-test is not writable (which it probably isn't), it is necessary to specify --vardir=<some writable directory>, I think this is ok as far as packaging goes as it is just the way mysql-test-run works currently.

For the apparmor issue, I files a separate bug: Bug#491349

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