Project

General

Profile

Actions
Copy link

Defect #19344

closed

MySQL 5.6: IssueNestedSetConcurrencyTest#test_concurrency : always fails

Added by Rupesh J almost 10 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Database
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Duplicate
Affected version:
3.0.0

Description

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.

Related issues

Related to Redmine - Feature #17460: MySQL 5.7 supportClosedMarius BĂLTEANU

Actions
Related to Redmine - Feature #19395: Support MariaDBNew

Actions
Related to Redmine - Defect #6579: Tree hierachy being currupted on multiple submissions of an issueClosedJean-Philippe Lang2010-10-05

Actions
Related to Redmine - Defect #23318: #lock_nested_set very slow on mysql with thousands of subtasksClosedJean-Philippe Lang

Actions
Related to Redmine - Defect #39437: MySQL / MariaDB issue nested set deadlocks and consistencyClosedMarius BĂLTEANU

Actions
Has duplicate Redmine - Defect #23942: Test: Mysql2::Error: Deadlock found when trying to get lockClosed

Actions
Actions
Copy link
 #1

Updated by Toshi MARUYAMA almost 10 years ago

  • Status changed from New to Needs feedback

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)
Actions
Copy link
 #2

Updated by Toshi MARUYAMA almost 10 years ago

  • Category set to Database
  • Status changed from Needs feedback to New

#17460#note-7

it does not pass the issue concurrency test (dead locks) ...

Actions
Copy link
 #3

Updated by Toshi MARUYAMA almost 10 years ago

  • Subject changed from IssueNestedSetConcurrencyTest#test_concurrency : Always fails on standard redmine installation. to MySQL : 5.6: IssueNestedSetConcurrencyTest#test_concurrency : always fails
Actions
Copy link
 #4

Updated by Toshi MARUYAMA almost 10 years ago

  • Subject changed from MySQL : 5.6: IssueNestedSetConcurrencyTest#test_concurrency : always fails to MySQL 5.6: IssueNestedSetConcurrencyTest#test_concurrency : always fails
Actions
Copy link
 #5

Updated by Toshi MARUYAMA almost 10 years ago

Actions
Copy link
 #6

Updated by Toshi MARUYAMA almost 10 years ago

This test fails on MariaDB 5.5, too.

On my CentOS7:

$ rpm -q mariadb
mariadb-5.5.41-2.el7_0.x86_64

Actions
Copy link
 #7

Updated by Toshi MARUYAMA almost 10 years ago

Actions
Copy link
 #8

Updated by Toshi MARUYAMA almost 9 years ago

  • Related to Defect #6579: Tree hierachy being currupted on multiple submissions of an issue added
Actions
Copy link
 #9

Updated by Toshi MARUYAMA about 8 years ago

  • Has duplicate Defect #23942: Test: Mysql2::Error: Deadlock found when trying to get lock added
Actions
Copy link
 #10

Updated by Toshi MARUYAMA about 8 years ago

  • Related to Defect #23318: #lock_nested_set very slow on mysql with thousands of subtasks added
Actions
Copy link
 #11

Updated by C S about 3 years ago

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

Actions
Copy link
 #12

Updated by C S about 3 years ago

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

Actions
Copy link
 #13

Updated by C S about 1 year ago

There are any news?

Actions
Copy link
 #14

Updated by Go MAEDA about 1 year ago

  • Related to Defect #39437: MySQL / MariaDB issue nested set deadlocks and consistency added
Actions
Copy link
 #15

Updated by Marius BĂLTEANU about 1 year ago

C S wrote in #note-13:

There are any news?

Only those from #39437.

Actions
Copy link
 #16

Updated by Marius BĂLTEANU about 1 year ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

This issue is fixed in the upcoming Redmine 5.1.1 (it will be released soon) and 6.0.0, but it may require some changes to the database settings, please see all the comments from #39437 and the MySQL_configuration page.

I'm closing this as duplicate.

Actions
Copy link

Also available in: Atom PDF