Bug #41509 falcon_bug_22212 fails sporadically: query 'reap' succeeded - should have failed
Submitted: 16 Dec 2008 14:25 Modified: 18 Dec 2008 23:34
Reporter: Sven Sandberg Email Updates:
Status: Can't repeat Impact on me:
None 
Category:Tests: Engine Severity:S7 (Test Cases)
Version:6.0 OS:Any
Assigned to: CPU Architecture:Any
Tags: F_ISOLATION, falcon_bug_22212, pushbuild, sporadic, test failure

[16 Dec 2008 14:25] Sven Sandberg
Description:
falcon_bug_22212 fails sporadically with this message:

falcon.falcon_bug_22212                  [ fail ]

CURRENT_TEST: falcon.falcon_bug_22212
mysqltest: At line 75: query 'reap' succeeded - should have failed with errno 1020...

The result from queries just before the failure was:
< snip >
# Establish connection con2 (user=root)
SET FALCON_CONSISTENT_READ=ON;
SET AUTOCOMMIT = 0;
# Switch to connection con1
UPDATE t1 SET x = 'Update by con1' WHERE id = 0;
# Switch to connection con2
# The following UPDATE t1 SET x = 'Update by con2' WHERE id = 0 is sent without
# waiting of the client (for this session) for completion.
# That means if you see the statement printed in the protocoll
# the outcome of the statement is unknown and no following server
# message etc. does not mean that the statement was successful
# completed.
UPDATE t1 SET x = 'Update by con2' WHERE id = 0;;
# Switch to connection con1
COMMIT;
# Switch to connection con2
# Here the connection prints the outcome of the preceeding
# UPDATE t1 SET x = 'Update by con2' WHERE id = 0;
# If there is nothing printed before the next statement (COMMIT)
# appears the outcome was success.

More results from queries before failure can be found in e:\var-falcon-102\log\falcon_bug_22212.log

 - saving 'e:/var-falcon-102/log/falcon.falcon_bug_22212/' to 'e:/var-falcon-102/log/falcon.falcon_bug_22212/'

Retrying test, attempt(2/3)...

How to repeat:
https://intranet.mysql.com/secure/pushbuild/showpush.pl?dir=bzr_mysql-6.0-rpl&order=85 vm-win2003-32-a/falcon
Happens in all 6.0 trees, xref: http://tinyurl.com/5qj3wa