test suite failures

Asked by Pavel Stratil on 2010-06-12

Hi everyone. I wonder, whats the current state of the test suite in Drizzle? 15 failures out of 322 tests, most of them similar .... seems like the test suite is broken (?) a sample of 'cat build.log | grep fail' gives:

   * Warnings as failure: yes
main.connect [ fail ]
drizzletest: At line 19: query 'connect fail_con,localhost,root,z,test2' failed with wrong errno 1045: 'Access denied for user 'root'@'127.0.0.1' (using password: YES)', instead of 1049...
The result from queries just before the failure was:
More results from queries before failure can be found in /var/tmp/portage/dev-db/drizzle-2010.06.1607/work/drizzle-2010.06.1607/tests/var/log/connect.log
main.data_dictionary_like_info [ fail ]
drizzletest: At line 36: query 'connect user3,localhost,mysqltest_2,,' failed: 1045: Access denied for user 'mysqltest_2'@'127.0.0.1' (using password: NO)
The result from queries just before the failure was:
More results from queries before failure can be found in /var/tmp/portage/dev-db/drizzle-2010.06.1607/work/drizzle-2010.06.1607/tests/var/log/data_dictionary_like_info.log
main.information_schema [ fail ]
drizzletest: At line 31: query 'connect user3,localhost,mysqltest_2,,' failed: 1045: Access denied for user 'mysqltest_2'@'127.0.0.1' (using password: NO)
The result from queries just before the failure was:
More results from queries before failure can be found in /var/tmp/portage/dev-db/drizzle-2010.06.1607/work/drizzle-2010.06.1607/tests/var/log/information_schema.log
main.lowercase_fs_off [ fail ]
drizzletest: At line 10: query 'connect sample,localhost,sample,password,d1' failed: 1045: Access denied for user 'sample'@'127.0.0.1' (using password: YES)
The result from queries just before the failure was:
More results from queries before failure can be found in /var/tmp/portage/dev-db/drizzle-2010.06.1607/work/drizzle-2010.06.1607/tests/var/log/lowercase_fs_off.log
simple_user_policy.basic [ fail ]
drizzletest: At line 20: query 'connect should_succeed,localhost,user1,,user1,,' failed: 1045: Access denied for user 'user1'@'127.0.0.1' (using password: NO)
The result from queries just before the failure was:
More results from queries before failure can be found in /var/tmp/portage/dev-db/drizzle-2010.06.1607/work/drizzle-2010.06.1607/tests/var/log/basic.log
schema_dictionary.data_dictionary [ fail ]
registry_dictionary.data_dictionary [ fail ]
drizzletest: At line 9: query 'SELECT count(*) FROM modules' failed: 20: drizzle_state_read:lost connection to server (EOF)
The result from queries just before the failure was:
More results from queries before failure can be found in /var/tmp/portage/dev-db/drizzle-2010.06.1607/work/drizzle-2010.06.1607/tests/var/log/data_dictionary.log
registry_dictionary.slap [ fail ]
drizzletest: At line 5: command "$DRIZZLE_SLAP --silent --concurrency=5 --iterations=20 --query="select * from data_dictionary.modules" --delimiter=";"" failed
The result from queries just before the failure was:
exec of '.././tests/var/../../client/drizzleslap -uroot --port=9800 --silent --concurrency=5 --iterations=20 --query="select * from data_dictionary.modules" --delimiter=";"' failed, error: 256, status: 1, errno: 11
More results from queries before failure can be found in /var/tmp/portage/dev-db/drizzle-2010.06.1607/work/drizzle-2010.06.1607/tests/var/log/slap.log
mysql_protocol.prototest [ fail ]
+FAILED (failures=2, errors=11)
logging_stats.command [ fail ]
drizzletest: At line 40: query 'connect con2, localhost, drizzle,,' failed: 1045: Access denied for user 'drizzle'@'127.0.0.1' (using password: NO)
The result from queries just before the failure was:
More results from queries before failure can be found in /var/tmp/portage/dev-db/drizzle-2010.06.1607/work/drizzle-2010.06.1607/tests/var/log/command.log
logging_stats.cumulative [ fail ]
drizzletest: At line 2: query 'connect con1, localhost, drizzle,,' failed: 1045: Access denied for user 'drizzle'@'127.0.0.1' (using password: NO)
logging_stats.max_session [ fail ]
drizzletest: At line 9: query 'connect con2, localhost, drizzle,,' failed: 1045: Access denied for user 'drizzle'@'127.0.0.1' (using password: NO)
The result from queries just before the failure was:
More results from queries before failure can be found in /var/tmp/portage/dev-db/drizzle-2010.06.1607/work/drizzle-2010.06.1607/tests/var/log/max_session.log
logging_stats.max_user [ fail ]
drizzletest: At line 15: query 'connect con3, localhost, $2,,' failed: 1045: Access denied for user '1'@'127.0.0.1' (using password: NO)
The result from queries just before the failure was:
More results from queries before failure can be found in /var/tmp/portage/dev-db/drizzle-2010.06.1607/work/drizzle-2010.06.1607/tests/var/log/max_user.log
auth_test.basic [ fail ]
drizzletest: At line 12: query 'connect password_ok,localhost,password_ok,test,,' failed: 1044: Access denied for user 'password_ok'@'127.0.0.1' to database 'test'
The result from queries just before the failure was:
More results from queries before failure can be found in /var/tmp/portage/dev-db/drizzle-2010.06.1607/work/drizzle-2010.06.1607/tests/var/log/basic.log
auth_file.basic [ fail ]
drizzletest: At line 7: query 'connect auth_file,localhost,auth_file,,,' failed: 1044: Access denied for user 'auth_file'@'127.0.0.1' to database 'test'
The result from queries just before the failure was:
More results from queries before failure can be found in /var/tmp/portage/dev-db/drizzle-2010.06.1607/work/drizzle-2010.06.1607/tests/var/log/basic.log

Any comments please?
TIA, Pavel

Question information

Language:
English Edit question
Status:
Solved
For:
Drizzle Edit question
Assignee:
No assignee Edit question
Solved by:
Pavel Stratil
Solved:
2010-09-06
Last query:
2010-09-06
Last reply:
2010-06-13
Patrick Crews (patrick-crews) said : #1

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.

Patrick Crews (patrick-crews) said : #2

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.

Joe Daly (skinny.moey) said : #4

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

Joe Daly (skinny.moey) said : #5

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.