MySQL Bugs: #21998: SELECT count() on information_schema delivers unexpected number in nist tests.

Bug #21998	SELECT count() on information_schema delivers unexpected number in nist tests.
Submitted:	4 Sep 2006 14:54	Modified:	2 Nov 2006 11:43
Reporter:	Horst Hunger	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Information schema	Severity:	S2 (Serious)
Version:	5.0.24a	OS:	Linux (Suse 10.1)
Assigned to:		CPU Architecture:	Any

Description:
The following SQL statement delivers the value 3 instead of 1, as "ist001" of the nist tests expects:

SELECT COUNT(*) FROM INFORMATION_SCHEMA.TABLES A
WHERE NOT EXISTS (
SELECT * FROM INFORMATION_SCHEMA.COLUMNS B
WHERE A.TABLE_SCHEMA = B.TABLE_SCHEMA
AND A.TABLE_NAME = B.TABLE_NAME) ;

...
TEST-INFO: MySQL expectations violated , result got:3 expected: 1

How to repeat:
run the nist tests by getting the "mysql-test-extra-5.0" (bk clone),
cd to "mysql-test in your Mysql 5.0.24a tree,
ln -s suite of "mysql-test-extra-5.0" (to suite), 
execute "perl mysql-test-run.pl --force --suite=nist"

or

 wait until I can offer a small test program reproducing the bug (see comments).

Thank you for a problem report. I've got failute of the test suite you used, but it is defferent (and there is no test you mentioned in current bk clone):

openxs@suse:~/dbs/5.0/mysql-test> perl mysql-test-run.pl --force --suite=nist
Logging: mysql-test-run.pl --force --suite=nist
Using ndbcluster if necessary, mysqld supports it
Skipping SSL, mysqld not compiled with SSL
Using MTR_BUILD_THREAD = 0
Using MASTER_MYPORT    = 9306
Using MASTER_MYPORT1   = 9307
Using SLAVE_MYPORT     = 9308
Using SLAVE_MYPORT1    = 9309
Using SLAVE_MYPORT2    = 9310
Using NDBCLUSTER_PORT  = 9350
Using IM_PORT          = 9311
Using IM_MYSQLD1_PORT  = 9312
Using IM_MYSQLD2_PORT  = 9314
Killing Possible Leftover Processes
Removing Stale Files
Installing Master Database
Installing Master Database
Saving snapshot of installed databases
=======================================================
Finding  Tests in the 'nist' suite
Starting Tests in the 'nist' suite

TEST                           RESULT
-------------------------------------------------------

nist_all                       [ fail ]

Errors are (from /home/openxs/dbs/5.0/mysql-test/var/log/mysqltest-time) :
mysqltest: In included file "./suite/nist/include/nist-env.inc": At line 261: qu
ery 'DROP USER $new_dba@localhost' failed with wrong errno 1470: 'String 'CANWEP
ARSELENGTH18' is too long for user name (should be no longer than 16)', instead
of 0...
(the last lines may be the most important ones)
Result from queries before failure can be found in /home/openxs/dbs/5.0/mysql-te
st/suite/nist/r/nist_all.log

Killing Possible Leftover Processes
Restoring snapshot of databases
Resuming Tests

nist_data                      [ fail ]

Errors are (from /home/openxs/dbs/5.0/mysql-test/var/log/mysqltest-time) :
mysqltest: In included file "./suite/nist/include/nist-env.inc": At line 261: qu
ery 'DROP USER $new_dba@localhost' failed with wrong errno 1470: 'String 'CANWEP
ARSELENGTH18' is too long for user name (should be no longer than 16)', instead
of 0...
(the last lines may be the most important ones)
Result from queries before failure can be found in /home/openxs/dbs/5.0/mysql-te
st/suite/nist/r/nist_data.log

Killing Possible Leftover Processes
Restoring snapshot of databases
Resuming Tests

-------------------------------------------------------
Ending Tests
Shutting-down Instance Manager
Shutting-down MySQL daemon

Master(s) shutdown finished
Slave(s) shutdown finished
Failed 2/2 tests, 0.00% were successful.

The log files in var/log may give you some hint
of what went wrong.
If you want to report this error, please read first the documentation at
http://www.mysql.com/doc/en/MySQL_test_suite.html

mysql-test-run in default mode: *** Failing the test(s): nist_all nist_data
mysql-test-run: *** ERROR: there where failing test cases

So, please, send a small test case that demonstrates the behaviour described.

Hi Valeriy,
I will send a small testcase as soon as possible.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".