MySQL Bugs: #38287: rpl_stm_flsh_tbls failed sporadically on pushbuild: server crash

Bug #38287	rpl_stm_flsh_tbls failed sporadically on pushbuild: server crash
Submitted:	22 Jul 2008 16:40	Modified:	19 Dec 2008 9:50
Reporter:	Sven Sandberg	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	Tests: Replication	Severity:	S7 (Test Cases)
Version:	6.0-rpl	OS:	Any
Assigned to:	Sven Sandberg	CPU Architecture:	Any
Tags:	pushbuild, rlp_stm_flsh_tbls, server crash, server has gone away, sporadic, test failure

Description:

rpl.rpl_stm_flsh_tbls          [ fail ]

CURRENT_TEST: rpl.rpl_stm_flsh_tbls
mysqltest: In included file ".\extra\rpl_tests\rpl_flsh_tbls.test": At line 53: query 'stop slave' failed with wrong errno 2006: 'MySQL server has gone away', instead of 1192...

The result from queries just before the failure was:
< snip >
rename table t1 to t5, t2 to t1;
flush no_write_to_binlog tables;
SHOW BINLOG EVENTS FROM 657 ;
Log_name	Pos	Event_type	Server_id	End_log_pos	Info
master-bin.000001	#	Query	1	#	use `test`; rename table t1 to t5, t2 to t1
select * from t3;
a
flush tables;
SHOW BINLOG EVENTS FROM 657 ;
Log_name	Pos	Event_type	Server_id	End_log_pos	Info
master-bin.000001	#	Query	1	#	use `test`; rename table t1 to t5, t2 to t1
master-bin.000001	#	Query	1	#	use `test`; flush tables
select * from t3;
a
stop slave;
drop table t1;
flush tables with read lock;
start slave;
stop slave;
ERROR HY000: MySQL server has gone away

More results from queries before failure can be found in e:\var-n_mix-100\log\rpl_stm_flsh_tbls.log

Stopping all servers...

How to repeat:
xref: http://tinyurl.com/6maha9

Suggested fix:
Impossible to debug since no logs are left on server. Awaiting fix to BUG#38181.

One failure is here:
https://intranet.mysql.com/secure/pushbuild/showpush.pl?dir=bzr_mysql-6.0-rpl&order=27 'vm-win2003-64-b' Win64 VS2005 -max-nt/n_mix

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

Setting to "Can't repeat" since this has not happened since July 2008.