Bug #56594 "Lock tables" is claimed not to work in the embedded server

Submitted: 6 Sep 2010 12:54 Modified: 20 Sep 2010 11:56
Reporter: Joerg Bruehe Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Locking Severity:S2 (Serious)
Version:5.5.6-m3 OS:Linux (icc x86)
Assigned to: Assigned Account CPU Architecture:Any

[6 Sep 2010 12:54] Joerg Bruehe
Description:
This test failure seems to be new in the 5.5.6-m3 release build.

It is specific to the platform Linux/x86/ICC and happens in the "embedded" test run only.
Given the identical platform, it might be related to bug#52419, but other than the platform and the inconsistency in the messages I have no hard evidence for this.

=====
main.lock_tables_lost_commit             [ fail ]
        Test ended at 2010-09-02 19:57:13

CURRENT_TEST: main.lock_tables_lost_commit
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use InnoDB's own implementation
InnoDB: Compressed tables use zlib 1.2.3
100902 20:57:06  InnoDB: Using Linux native AIO
100902 20:57:06  InnoDB: highest supported file format is Barracuda.
mysqltest: At line 17: query 'INSERT INTO t1 VALUES(10)' failed: 1100: Table 't1' was not locked with LOCK TABLES

The result from queries just before the failure was:
DROP TABLE IF EXISTS t1;
CREATE TABLE t1(a INT) ENGINE=innodb;
LOCK TABLES t1 WRITE;

Warnings from just before the error:
Note 1051 Unknown table 't1'

 - saving '/export/home2/pb2/test/sb_2-2235639-1283447973.31/mysql-5.5.6-rc-linux2.6-i686-icc/mysql-test/var/log/main.lock_tables_lost_commit/' to '/export/home2/pb2/test/sb_2-2235639-1283447973.31/mysql-5.5.6-rc-linux2.6-i686-icc/mysql-test/var/log/main.lock_tables_lost_commit/'

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

So the sequence is "create", "lock", insert", all about table "t1";
the warning "unknown table" seems to come with the "lock" just after "create",
and then "insert" fails due to a missing lock.

Further in the test suite, there are more failures where "was not locked" is claimed.

How to repeat:
Run the suite on this platform, in "embedded" mode.

Suggested fix:
Do ICC builds in PB2 for faster problem discovery.
[20 Sep 2010 11:56] Joerg Bruehe
From the symptoms this isn't obvious, but this was (most probably) just another effect of bad atomic ops as diagnosed with bug#52419.

So I set this one as "duplicate".

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.