| Bug #53238 | mdl_sync fails sporadically | ||
|---|---|---|---|
| Submitted: | 28 Apr 2010 8:43 | Modified: | 12 Jul 2010 17:10 |
| Reporter: | Alexander Nozdrin | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Locking | Severity: | S3 (Non-critical) |
| Version: | M3 (Celosia) | OS: | Any |
| Assigned to: | Dmitry Lenev | CPU Architecture: | Any |
| Tags: | pb2, sporadic, test failure | ||
[28 Apr 2010 9:51]
Valeriy Kravchuk
I can not repeat this with current mysql-trunk tree on my Ubuntu 8.04.4.
[29 Apr 2010 5:26]
Sveta Smirnova
Thank you for the report. Verified as logged in pushbuild, although I could not reepat this in my environment a s well.
[26 May 2010 18:51]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/109303 3023 Dmitry Lenev 2010-05-26 Fix for bug #53238 "mdl_sync fails sporadically". The problem was that mdl_sync.test was failing sporadically, due to fact that part of the test didn't take into account effects of MyISAM's concurrent insert. This patch solves the problem by making test case robust against concurrent insert.
[26 May 2010 19:58]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/109306 3025 Dmitry Lenev 2010-05-26 Fix for bug #53238 "mdl_sync fails sporadically". The problem was that mdl_sync.test was failing sporadically, due to fact that part of the test didn't take into account effects of MyISAM's concurrent insert. This patch solves the problem by making test case robust against concurrent insert.
[22 Jun 2010 13:07]
Bugs System
Pushed into 5.5.5-m3 (revid:alik@sun.com-20100622130139-u05awgya93zvbsop) (version source revid:marko.makela@oracle.com-20100603095032-v5ptkkzt1bhz0m1d) (merge vers: 5.1.48) (pib:16)
[22 Jun 2010 13:09]
Bugs System
Pushed into mysql-next-mr (revid:alik@sun.com-20100622130623-r7yhm89fz9n5t9nb) (version source revid:alik@sun.com-20100622130528-187gd949sa9b6pa6) (pib:16)
[12 Jul 2010 17:10]
Paul DuBois
Changes for test case. No changelog entry needed.
Description: main.mdl_sync [ fail ] Test ended at 2010-04-28 04:02:15 CURRENT_TEST: main.mdl_sync --- /export/home/pb2/test/sb_1-1733555-1272418051.32/mysql-5.5.5-m3-linux-i686-test/mysql-test/r/mdl_sync.result 2010-04-27 16:20:41.000000000 +0300 +++ /export/home/pb2/test/sb_1-1733555-1272418051.32/mysql-5.5.5-m3-linux-i686-test/mysql-test/r/mdl_sync.reject 2010-04-28 05:02:14.000000000 +0300 @@ -332,7 +332,7 @@ c1 select count(*) from t1; count(*) -4 +3 insert into t1 values (1); # Check that SNW lock is not compatible with SW lock. # Again we use ALTER TABLE which fails after opening mysqltest: Result content mismatch - saving '/export/home/pb2/test/sb_1-1733555-1272418051.32/mysql-5.5.5-m3-linux-i686-test/mysql-test/var-n_mix/log/main.mdl_sync/' to '/export/home/pb2/test/sb_1-1733555-1272418051.32/mysql-5.5.5-m3-linux-i686-test/mysql-test/var-n_mix/log/main.mdl_sync/' Retrying test, attempt(2/3)... main.mdl_sync [ retry-pass ] 7838 Retrying test, attempt(3/3)... main.mdl_sync [ retry-pass ] 6027 How to repeat: Reported after failure in the following build (in mysql-trunk): http://pb2.norway.sun.com/web.py?template=push_details&push=1201442 Log: http://pb2.norway.sun.com/web.py?action=archive_download&archive_id=1737925&pretty=please