MySQL Bugs: #18903: test fails: binlog_row_drop_tmp

Bug #18903	test fails: binlog_row_drop_tmp_tbl with --binlog-format=row
Submitted:	8 Apr 2006 10:42	Modified:	9 Jul 2008 19:40
Reporter:	Andrei Elkin	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: Row Based Replication ( RBR )	Severity:	S3 (Non-critical)
Version:	mysql-5.1-release (5.1.9)	OS:	Linux (FC4)
Assigned to:	Mats Kindahl	CPU Architecture:	Any

Description:
Running make test on mysql-5.1-release (5.1.9) on dl145k.mysql (AMD Opteron) yielded a failure.
Innitially I got the failure with autopushing my fix for #17284. I rolled my fix back
to test on pure clone with the last changeset
ChangeSet@1.2306.1.1, 2006-04-08 04:29:17+02:00, kent@mysql.com
Still the same:

TEST                            RESULT
-------------------------------------------------------
binlog_row_drop_tmp_tbl        [ fail ]

Errors are (from /users/aelkin/FIXES/mysql-5.1-release.17284/mysql-test/var/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/binlog_row_drop_tmp_tbl.result    2006-04-07 17:12:43.000000000 +0300
--- r/binlog_row_drop_tmp_tbl.reject    2006-04-08 13:32:05.000000000 +0300
***************
*** 14,18 ****
--- 14,20 ----
  show binlog events;
  Log_name      Pos     Event_type      Server_id       End_log_pos     Info
  master-bin.000001     #       Format_desc     1       #       Server ver: VERSION, Binlog ver: 4
+ master-bin.000001     #       Table_map       1       #       table_id: # (mysql.proc)
+ master-bin.000001     #       Write_rows      1       #       table_id: # flags: STMT_END_F
  master-bin.000001     #       Query   1       #       create database `drop-temp+table-test`
  drop database `drop-temp+table-test`;
-------------------------------------------------------

How to repeat:
./mysql-test-run --mysqld=--binlog-format=row binlog_row_drop_tmp_tbl

Thank you for a problem report. This test "passed" on today's 5.1-debug-BK (ChangeSet@1.2303.1.1, 2006-04-09 19:43:36-07:00) on SuSE 9.3, i686. Please, check the latest BK build on your platfrom:

openxs@suse:~/dbs/5.1/mysql-test> ./mysql-test-run --mysqld=--binlog-format=row
 binlog_row_drop_tmp_tbl
Logging: ./mysql-test-run --mysqld=--binlog-format=row binlog_row_drop_tmp_tbl
Stopping master cluster
Installing Test Databases
Removing Stale Files
Installing Master Databases
running  ../libexec/mysqld --no-defaults --bootstrap --skip-grant-tables     --basedir=.. --datadir=mysql-test/var/master-data --skip-innodb --skip-ndbcluster --skip-bdb
Installing Master Databases 1
running  ../libexec/mysqld --no-defaults --bootstrap --skip-grant-tables     --basedir=.. --datadir=mysql-test/var/master-data1 --skip-innodb --skip-ndbcluster
--skip-bdb
Installing Slave Databases
running  ../libexec/mysqld --no-defaults --bootstrap --skip-grant-tables     --basedir=.. --datadir=mysql-test/var/slave-data --skip-innodb --skip-ndbcluster --skip-bdb
Manager disabled, skipping manager start.
Loading Standard Test Databases
Starting Tests

TEST                            RESULT
-------------------------------------------------------
binlog_row_drop_tmp_tbl        [ pass ]
-------------------------------------------------------

Ending Tests
Shutting-down MySQL daemon

Master shutdown finished
Slave shutdown finished
All 1 tests were successful.
WARNING: Got errors/warnings while running tests. Please examine
/home/openxs/dbs/5.1/mysql-test/var/log/warnings for details.

openxs@suse:~/dbs/5.1/mysql-test> tail var/log/warnings
Warning: Not freed memory segments: 44
Warning: Memory that was not free'ed (2464 bytes):
openxs@suse:~/dbs/5.1/mysql-test> uname -a
Linux suse 2.6.11.4-20a-default #1 Wed Mar 23 21:52:37 UTC 2005 i686 i686 i386 GNU/Linux

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".

This test fails intermittently (but fairly consistently) during pushbuild on Solaris 10 AMD64 -max GCC. Looks like the test isn't quite deterministic.

Last seen failure was 2007-09-12 15:10:27, and the failure was not the same. Since the test has not failed since then, I consider it fixed. Please reopen the bug if another failure is seen.