Your message dated Sun, 13 May 2012 05:03:02 +0100
with message-id <[email protected]>
and subject line done
has caused the Debian Bug report #366701,
regarding mysql-test-run test suite doesn't pass (or even run)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
366701: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=366701
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mysql-dfsg-5.0
Version: 5.0.21-2

Mysql sources include a comprehensive test suite in the mysql-test
subdirectory.  As part of the debian build process, this is not run.
I don't consider this fact a bug, because the test suite takes ages to
run even on a big machine.

However, running the test manually after building (before installing),
the test suite does not pass.  The first test that fails is 'create':

/home/wg/Debian/mysql-dfsg-5.0-5.0.21/mysql-test% ./mysql-test-run
Logging: ./mysql-test-run 
Installing Test Databases
Removing Stale Files
Installing Master Databases
running  ../sql/mysqld --no-defaults --bootstrap --skip-grant-tables     
--basedir=. --datadir=./var/master-data --skip-innodb --skip-ndbcluster 
--skip-bdb     --language=../sql/share/english/ 
--character-sets-dir=../sql/share/charsets/
Installing Master Databases 1
running  ../sql/mysqld --no-defaults --bootstrap --skip-grant-tables     
--basedir=. --datadir=./var/master-data1 --skip-innodb --skip-ndbcluster 
--skip-bdb     --language=../sql/share/english/ 
--character-sets-dir=../sql/share/charsets/
Installing Slave Databases
running  ../sql/mysqld --no-defaults --bootstrap --skip-grant-tables     
--basedir=. --datadir=./var/slave-data --skip-innodb --skip-ndbcluster 
--skip-bdb     --language=../sql/share/english/ 
--character-sets-dir=../sql/share/charsets/
Manager disabled, skipping manager start.
Starting ndbcluster
Starting ndbd
Starting ndbd
Waiting for started...
NDBT_ProgramExit: 0 - OK
Connected to Management Server at: localhost:9350
Cluster Configuration
---------------------
[ndbd(NDB)]     2 node(s)
id=1    @127.0.0.1  (Version: 5.0.21, Nodegroup: 0, Master)
id=2    @127.0.0.1  (Version: 5.0.21, Nodegroup: 0)

[ndb_mgmd(MGM)] 1 node(s)
id=3    @127.0.0.1  (Version: 5.0.21)

[mysqld(API)]   4 node(s)
id=4 (not connected, accepting connect from any host)
id=5 (not connected, accepting connect from any host)
id=6 (not connected, accepting connect from any host)
id=7 (not connected, accepting connect from any host)

Loading Standard Test Databases
Starting Tests

TEST                            RESULT
-------------------------------------------------------
alias                          [ pass ]   
alter_table                    [ pass ]   
... [many more passes]
count_distinct3                [ pass ]   
create                         [ fail ]

Errors are (from 
/home/wg/Debian/mysql-dfsg-5.0-5.0.21/mysql-test/var/log/mysqltest-time) :
mysqltest: At line 410: Could not open connection 'user1': 1045 Access denied 
for user 'mysqltest_1'@'localhost' (using password: NO)
(the last lines may be the most important ones)

When running the test suite with --force, there are many more, similar
failures (in total, about 8% of all tests fail).

I have verified this behaviour on two completely different systems,
one which is basically woody with gcc-2.95, and one which is basically
sarge with gcc-4.0.

Of course, the failures may be harmless and caused by a debian patch,
however in that case a note should be added in the debian subdirectory
(I couldn't find anything on running the test suite there).

Thanks,
Wolfram.



--- End Message ---
--- Begin Message --- I have successfully used the test suite out of the box. The one thing I did have to do is set the vardir argument. However I can think of no sensible default for that.

As this is quite old and the discussions now probably irrelevant I am closing the bug.


--- End Message ---

Reply via email to