プロジェクト

全般

プロフィール

Vote #76172

未完了

MySQL 5.6: IssueNestedSetConcurrencyTest#test_concurrency : always fails

Admin Redmine さんが約4年前に追加. 約4年前に更新.

ステータス:
New
優先度:
通常
担当者:
-
カテゴリ:
Database_21
対象バージョン:
-
開始日:
2022/05/09
期日:
進捗率:

0%

予定工数:
category_id:
21
version_id:
0
issue_org_id:
19344
author_id:
84718
assigned_to_id:
0
comments:
12
status_id:
1
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
80
ステータス-->[New]

説明

Hello,

When I run rake test:units
I always get this test failure. Can you please correct this.

1) Failure:
IssueNestedSetConcurrencyTest#test_concurrency [E:/REDMINE/DEV3.0/redmine/test/unit/issue_nested_set_concurrency_test.rb:45]:
Expected "Mysql2::Error: Deadlock found when trying to get lock; try restarting transaction: SELECT issues.id FROM issues WHERE (root_id IN (SEL
ECT root_id FROM issues WHERE id IN (390,388))) ORDER BY issues.id ASC FOR UPDATE" to be nil.

Redmine : 3.0.0
MySql : 5.6.14

Thanks.


journals

I cannot reproduce on my Windows 8.1 Pro.

* 5.5.40 - MySQL Community Server (GPL)
* ruby 1.9.3p551 (2014-11-13) [i386-mingw32]
* mysql2 (0.3.18-x86-mingw32)

--------------------------------------------------------------------------------
#17460#note-7
> it does not pass the issue concurrency test (dead locks) ...
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This test fails on MariaDB 5.5, too.

On my CentOS7:
<pre>
$ rpm -q mariadb
mariadb-5.5.41-2.el7_0.x86_64
</pre>
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Since MySQL 5.6 was set as EOL in February 2021, it would make sense to stop supporting it, right?
--------------------------------------------------------------------------------
Is this Since MySQL 5.6 was set as EOL in February 2021, it would make sense to stop supporting it, right?
--------------------------------------------------------------------------------


related_issues

relates,New,17460,MySQL 5.7 support
relates,New,19395,Support MariaDB
relates,Closed,6579,Tree hierachy being currupted on multiple submissions of an issue
relates,Reopened,23318,#lock_nested_set very slow on mysql with thousands of subtasks
duplicates,Closed,23942,Test: Mysql2::Error: Deadlock found when trying to get lock

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0