MySQL Bugs: #46804: innodb test fails on PB-2 with a crash

Bug #46804	innodb test fails on PB-2 with a crash
Submitted:	19 Aug 2009 9:56	Modified:	10 Oct 2009 14:49
Reporter:	Andrei Elkin	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	5.0	OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	test failure

Description:
Failure on PB-2

http://pb2.norway.sun.com/web.py?template=mysql_show_test_failure&test_failure_id=2281048

has these details:

Where 	Build 	Test 	Run 	Suite 	Case 	Mode 	When
mysql-5.0-bugteam
490134	tree-max-win-x86_64-zip
490170 loki03	test-max-win_ws2008-x86_64
490348 loki05	ps_stm		innodb	None	2009-08-13 22:40:58
- Show/hide test output -
Original output

innodb                         [ fail ]

mysqltest: At line 1001: query 'update t1 set c=a' failed: 2013: Lost connection to MySQL server during query

How to repeat:
Look at the url.

Alas, there were no more details on the reported failure.
Searching the same pattern Innodb +  "Lost connection" via xref
opens quite a number links, e.g

http://pb2.norway.sun.com/web.py?template=mysql_show_test_failure&test_failure_id=22152

Where 	Build 	Test 	Run 	Suite 	Case 	Mode 	When
mysql-pe
414130	binary-max-sol10-sparc64-tar-gz
414424 takk-z8	test-max-sol10-sparc64
414812 astra06	ps_row	main	innodb	None	2009-06-16 13:35:07
- Show/hide test output -
Original output

main.innodb                              w3 [ fail ]
        Test ended at 2009-06-16 15:37:14

CURRENT_TEST: main.innodb
mysqltest: At line 872: query 'update t1,t2 set t1.b=t1.b+2,t2.b=t1.b+10 where t1.b between 3 and 5 and t1.a=t2.a+100' failed: 2013: Lost connection to MySQL server during query

The result from queries just before the failure was:
< snip >
108	8
109	9
110	10
111	11
112	12
update t1,t2 set t1.b=t1.b+10 where t1.b=2;

This failure - most certainly a crash - on mysql-pe looks the same as the reported on 5.0.
Again, it's pity,but PB2 did not supply any backtrace in either case.

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