MySQL Bugs: #7073: Test failure: 'system_mysql_db

Bug #7073	Test failure: 'system_mysql_db_fix' when using '--ps-protocol'
Submitted:	7 Dec 2004 12:51	Modified:	10 Dec 2004 10:12
Reporter:	Joerg Bruehe	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	4.1.8-pre	OS:	Several Unix
Assigned to:	Ramil Kalimullin	CPU Architecture:	Any

Description:
As asked by Kent, I subjected my current 4.1.8-pre version to this run:
  ./mysql-test-run --local --ps-protocol --force

The failure is:
= = = = =

system_mysql_db_fix            [ fail ]

Errors are (from /M41/push-4.1/mysql-test/var/log/mysqltest-time) :
/M41/push-4.1/scripts/mysql_fix_privilege_tables: line 1: --no-defaults: command not found
ERROR 1146 (42S02) at line 15: Table 'test.func' doesn't exist
ERROR 1146 (42S02) at line 16: Table 'test.columns_priv' doesn't exist
ERROR 1146 (42S02) at line 17: Table 'test.tables_priv' doesn't exist
ERROR 1054 (42S22) at line 30: Unknown column 'Grant_priv' in 'where clause'
ERROR 1054 (42S22) at line 84: Unknown column 'Type' in 'columns_priv'
ERROR 1060 (42S21) at line 90: Duplicate column name 'type'
ERROR 1054 (42S22) at line 98: Unknown column 'Show_db_priv' in 'where clause'
/M41/push-4.1/client/.libs/mysqltest: At line 77: Result length mismatch
(the last lines may be the most important ones)

Ending Tests
Shutting-down MySQL daemon

Master shutdown finished
Slave shutdown finished
Resuming Tests

= = = = =

Last changesets:

ChangeSet@1.2134, 2004-12-06 14:57:29+01:00, serg@serg.mylan
  Merge bk-internal.mysql.com:/home/bk/mysql-4.1/
  into serg.mylan:/usr/home/serg/Abk/mysql-4.1

ChangeSet@1.2132.1.1, 2004-12-06 14:51:38+01:00, serg@serg.mylan
  Merge bk-internal.mysql.com:/home/bk/mysql-4.1/
  into serg.mylan:/usr/home/serg/Abk/mysql-4.1

ChangeSet@1.2133, 2004-12-06 14:51:37+01:00, rburnett@build.mysql.com
  Merge bk-internal.mysql.com:/home/bk/mysql-4.1
  into build.mysql.com:/users/rburnett/mysql-4.1-new2

ChangeSet@1.2132, 2004-12-06 14:34:02+01:00, mskold@mysql.com
  New fix for bug#6796 Wrong outcome of update operation of ndb table

How to repeat:
See description.

Thank you for the bug report.

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

This was fixed in MySQL 4.1 tree resently
(Just checked and the 5.0 tree still has this problem. I will ensure that this is fixed before 5.0.3)

The fix for this is not yet pushed - I did another "pull" today, re-built, re-tested, and the problem still exists.

In tonight's "debug" build
 (fresh pull with latest changeset "1.2145.2.1 04/12/08 19:34:11 lenz@mysql.com +1 -0"),
the test failed on 26 platforms!

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

fixed in 4.1.8