test suite failures

I'll need a little more information to help you. Such as the source tree you used, what you did to build / install / test, etc.

Running:
bzr branch lp:drizzle
./config/autorun.sh && ./configure && make && make test results in these tests passing on my machine.

This appears to be a permissions issue and not related to the tests themselves. It could be related to how you installed / the permissions for the installation.

I'll need a little more information to help you. Such as the source tree you used, what you did to build / install / test, etc.

Running:
bzr branch lp:drizzle
./config/autorun.sh && ./configure && make && make test results in these tests passing on my machine.

This appears to be a permissions issue and not related to the tests themselves. It could be related to how you installed / the permissions for the installation.

Hmmm, I guess I should have tried that first. Let me test that with same configure options and I'll let you know.

I'm building drizzle with gentoo's portage. We drop privileges during compilation, not sure about the tests - seems that the tests may require root privileges. When you say "This appears to be a permissions issue and not related to the tests themselves. It could be related to how you installed / the permissions for the installation." .... then it cant be. Portage does basically something in the sense of ./configure && make && make test && make install, so it should have nothing to do with how I installed. Still I cant get rid of the idea that the test suite expects something that doesn't necessarily have to be present.

This looks like any test that changed user during the test failed. hmm

I would be interested if your still having problems of seeing if you get permission denied errors trying to login outside of the test suite. You can try to connect to the running server like:

jdaly@rx7:~/drizzle/repos/trunk-build/tests> ../client/drizzle --user=drizzle --port=9306

port 9306 is for a server that was started using:

jdaly@rx7:~/drizzle/repos/trunk-build/tests> ./dtr --start-and-exit

This would closely mimic what the tests are doing by default for the logging_stats test failures at least.

i did on trunk the following

./config/autorun.sh
./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --disable-all --disable-static --disable-dependency-tracking --disable-mtmalloc --enable-tcmalloc --enable-libmemcached --enable-libgearman --enable-libldap --with-auth-http-plugin --with-auth-pam-plugin --with-md5-plugin --with-gearman_udf-plugin --with-logging_gearman-plugin --with-memcache-functions-plugins --with-auth-ldap-plugin --with-logging-stats --without-hello-world-plugin --disable-pbxt-plugin --without-pbxt-plugin --disable-rabbitmq-plugin --without-rabbitmq-plugin --disable-embedded-innodb-plugin --without-embedded-innodb-plugin --enable-auth-test-plugin --with-auth-test-plugin --enable-auth-file-plugin --with-auth-file-plugin --enable-simple-user-policy-plugin --with-simple-user-policy-plugin --enable-logging-stats-plugin --with-logging-stats-plugin --enable-logging-syslog-plugin --with-logging-syslog-plugin
make && make test

the configure is a copy of what portage generates from my private development ebuild with most useflags enabled.
make test still fails (building as a normal user - if i'm not mistaken, building/testing as root should fail too since drizzled wont start by default when run as root).

Joe: will test that after yet another rebuild.

killua@vrrr ~/test/dr/drizzle/tests $ ./dtr --start-and-exit
Logging: ./dtr --start-and-exit
Drizzle Version 2010.06.1616
Using MTR_BUILD_THREAD = -69.4
Using MASTER_MYPORT = 9306
Using MASTER_MYPORT1 = 9307
Using SLAVE_MYPORT = 9308
Using SLAVE_MYPORT1 = 9309
Using SLAVE_MYPORT2 = 9310
Using MC_PORT = 9316
Killing Possible Leftover Processes
Removing Stale Files
Creating Directories
================================================================================
DEFAULT STORAGE ENGINE: innodb
TEST RESULT TIME (ms)
--------------------------------------------------------------------------------

Servers started, exiting
killua@vrrr ~/test/dr/drizzle/tests $ ../client/drizzle --user=drizzle --port=9306
ERROR 1045 (28000): Access denied for user 'drizzle'@'127.0.0.1' (using password: NO)
killua@vrrr ~/test/dr/drizzle/tests $

killua@vrrr ~/test/dr/drizzle/tests $ ps aux | grep drizz
killua 29483 0.4 1.4 418252 43856 pts/5 Sl 00:29 0:00 /home/killua/test/dr/drizzle/drizzled/.libs/drizzled --no-defaults --basedir=/home/killua/test/dr/drizzle/tests --default-storage-engine=innodb --secure-file-priv=/home/killua/test/dr/drizzle/tests/var --tmpdir=/home/killua/test/dr/drizzle/tests/var/tmp --mysql-protocol-connect-timeout=60 --user=root --pid-file=/home/killua/test/dr/drizzle/tests/var/run/master.pid --mysql-protocol-port=9306 --drizzle-protocol-port=9356 --datadir=/home/killua/test/dr/drizzle/tests/var/master-data --server-id=1 --loose-innodb_data_file_path=ibdata1:20M:autoextend --loose-innodb-lock-wait-timeout=5 --myisam_key_cache_size=1M --sort_buffer=256K --max_heap_table_size=1M --core-file
killua 29547 0.0 0.0 7692 844 pts/5 S+ 00:31 0:00 grep --colour=auto drizz

the situation remains in the 1634 build. Here the summary ....

Stopping All Servers
Failed 15/332 tests, 95.48% were successful.

The log files in var/log may give you some hint
of what went wrong.
If you want to report this error, go to:
 http://bugs.launchpad.net/drizzle
The servers were restarted 48 times
Spent 2028.406 of 3279 seconds executing testcases

mysql-test-run in default mode: *** Failing the test(s): main.connect main.data_dictionary_like_info main.drizzleslap main.information_schema main.lowercase_fs_off simple_user_policy.basic registry_dictionary.data_dictionary registry_dictionary.slap mysql_protocol.prototest logging_stats.command logging_stats.cumulative logging_stats.max_session logging_stats.max_user auth_test.basic auth_file.basic

....

resolved in current release.