MySQL Bugs: #29923: federated.test fails in 5.0-maint, 5.1-maint

Bug #29923	federated.test fails in 5.0-maint, 5.1-maint
Submitted:	20 Jul 2007 6:07	Modified:	13 Dec 2007 5:16
Reporter:	Ramil Kalimullin	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Tests	Severity:	S3 (Non-critical)
Version:	5.0, 5.1	OS:	Any
Assigned to:	Ramil Kalimullin	CPU Architecture:	Any
Tags:	pbfail

Description:
federated.test fails in 5.0-maint, 5.1-maint probably due to merging errors:

federated                      [ fail ]

Errors are (from /dev/shm/var-n_stm-130/log/mysqltest-time) :
mysqltest: Result length mismatch
(the last lines may be the most important ones)
Below are the diffs between actual and expected results:
-------------------------------------------------------
*** r/federated.result	Thu Jul 19 22:59:11 2007
--- r/federated.reject	Fri Jul 20 00:17:27 2007
***************
*** 1878,1883 ****
--- 1878,1885 ----
  categoryId
  1
  2
+ drop table federated.t1;
+ drop table federated.t1;

How to repeat:
Run the test.

Suggested fix:
Fix the result file.

http://lists.mysql.com/commits/31211

Below is the list of changes that have just been committed into a local
5.0 repository of ram. When ram does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://dev.mysql.com/doc/mysql/en/installing-source-tree.html

ChangeSet@1.2475, 2007-07-20 11:23:38+05:00, ramil@mysql.com +1 -0
  Fixed #29923: federated.test fails in 5.0-maint, 5.1-maint
  
  Result adjusted.

  mysql-test/r/federated.result@1.44, 2007-07-20 11:23:37+05:00, ramil@mysql.com +2 -0
    Fixed #29923: federated.test fails in 5.0-maint, 5.1-maint
      - result adjusted.

ok to push