MySQL Bugs: #18918: rpl000010 fails with --ps-protocol --binlog-format=row

Bug #18918	rpl000010 fails with --ps-protocol --binlog-format=row
Submitted:	9 Apr 2006 13:58	Modified:	6 Jun 2006 12:01
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:	5.1.10-beta	OS:	Linux (FC4)
Assigned to:	Andrei Elkin	CPU Architecture:	Any

Description:
rpl000010                      [ fail ]

Errors are (from /tmp/andrei/5.1/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/rpl000010.result  Sat Apr  8 22:38:24 2006
--- r/rpl000010.reject  Sun Apr  9 00:44:59 2006
***************
*** 10,14 ****
  select n from t1;
  n
  1
- 2
  drop table t1;
--- 10,13 ----
-------------------------------------------------------

How to repeat:
This one seems to be for very patients. I had to loop it several time to catch it at least twice again in a manner of the following:

bash-3.00$ for n in `seq 1 100`; do echo $n; ./mysql-test-run --ps-protocol --force  \ --mysqld=--binlog-format=row rpl000010 | grep 'fail'; done
1
...
22
rpl000010                      [ fail ]
23
rpl000010                      [ fail ]
...
100

Thank you for a problem report. It fails for me each and every time with 5.1-debug-BK (ChangeSet@1.2303.1.1, 2006-04-09 19:43:36-07:00) on SuSE 9.3:

openxs@suse:~/dbs/5.1/mysql-test> for n in `seq 1 100`; do echo $n; ./mysql-test-run --ps-protocol --force --mysqld=--binlog-format=row rpl000010 | grep 'fail
'; done
1
rpl000010                      [ fail ]
mysqltest: At line 7: query 'insert into t1 values(NULL)' failed: 2013: Lost con
nection to MySQL server during query
./mysql-test-run: line 1743: kill: (26461) - No such process
./mysql-test-run: line 1747: kill: (26461) - No such process

Th error message is different, though. Should be checked, anyway.

Now neither I nor Valeriy can repeat it. I am leaving extensive test to catch it once again.

I was not able to repeat with today's 5.1-BK (ChangeSet@1.2179.1.1, 2006-06-05 15:07:27-07:00).