Bug #37741 Test concurrent_innodb fails with invalid login
Submitted: 30 Jun 2008 14:12 Modified: 30 Jun 2008 14:41
Reporter: Joe Grasse Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Tests Severity:S3 (Non-critical)
Version:5.1.25 OS:Any
Assigned to: CPU Architecture:Any

[30 Jun 2008 14:12] Joe Grasse
Description:
Trying to run the test concurrent_innodb will fail because the secondary users it tries to connect with do not exist. As a side note, if the users are changed to root the connections will succeed, but the test will still fail with the following.

main.concurrent_innodb         [ fail ]

mysqltest: In included file "./include/concurrent.inc": At line 211: query 'update t1 set tipo=11+get_lock("hello",10)*0 where tipo=22' succeeded - should have failed with errno 1205...

The result from queries just before the failure was:
< snip >
insert into t1 values (8,8, "bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb");
insert into t1 values (10,1,"ccccccccccccccccccccccccccccccccccccccccccc");
insert into t1 values (20,2,"ddddddddddddddddddddddddddddddddddddddddddd");
insert into t1 values (30,1,"eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee");
insert into t1 values (40,2,"fffffffffffffffffffffffffffffffffffffffffff");
insert into t1 values (50,1,"ggggggggggggggggggggggggggggggggggggggggggg");
insert into t1 values (60,2,"hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh");
insert into t1 values (70,1,"iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii");
insert into t1 values (80,22,"jjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj");
insert into t1 values (90,11,"kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk");
select get_lock("hello",10);
get_lock("hello",10)
1
begin;
select * from t1 where tipo=2 FOR UPDATE;
begin;
select release_lock("hello");
release_lock("hello")
1
update t1 set tipo=11+get_lock("hello",10)*0 where tipo=22;

How to repeat:
Run:
mysql-test-run.pl --big-test --do-test=concurrent_innodb

Suggested fix:
Add the users before trying to connect with them, or change the usernames to root.
[30 Jun 2008 14:41] Sveta Smirnova
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Duplicate of bug #37635