Project

General

Profile

Actions

Defect #19344

closed

MySQL 5.6: IssueNestedSetConcurrencyTest#test_concurrency : always fails

Defect #19344: MySQL 5.6: IssueNestedSetConcurrencyTest#test_concurrency : always fails

Added by Rupesh J over 11 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Database
Target version:
-
Resolution:
Duplicate
Affected version:

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 6 (1 open — 5 closed)

Related to Redmine - Feature #17460: MySQL 5.7 supportClosedMarius BĂLTEANUActions
Related to Redmine - Feature #19395: Support MariaDBNewActions
Related to Redmine - Defect #6579: Tree hierachy being currupted on multiple submissions of an issueClosedJean-Philippe LangActions
Related to Redmine - Defect #23318: #lock_nested_set very slow on mysql with thousands of subtasksClosedJean-Philippe LangActions
Related to Redmine - Defect #39437: MySQL / MariaDB issue nested set deadlocks and consistencyClosedMarius BĂLTEANUActions
Has duplicate Redmine - Defect #23942: Test: Mysql2::Error: Deadlock found when trying to get lockClosedActions

Updated by Toshi MARUYAMA over 11 years ago Actions #1

  • 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)

Updated by Toshi MARUYAMA over 11 years ago Actions #2

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

#17460#note-7

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

Updated by Toshi MARUYAMA over 11 years ago Actions #3

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

Updated by Toshi MARUYAMA over 11 years ago Actions #4

  • Subject changed from MySQL : 5.6: IssueNestedSetConcurrencyTest#test_concurrency : always fails to MySQL 5.6: IssueNestedSetConcurrencyTest#test_concurrency : always fails

Updated by Toshi MARUYAMA over 11 years ago Actions #5

Updated by Toshi MARUYAMA over 11 years ago Actions #6

This test fails on MariaDB 5.5, too.

On my CentOS7:

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

Updated by Toshi MARUYAMA over 11 years ago Actions #7

Updated by Toshi MARUYAMA over 10 years ago Actions #8

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

Updated by Toshi MARUYAMA about 10 years ago Actions #9

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

Updated by Toshi MARUYAMA about 10 years ago Actions #10

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

Updated by C S about 5 years ago Actions #11

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

Updated by C S about 5 years ago Actions #12

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

Updated by C S about 3 years ago Actions #13

There are any news?

Updated by Go MAEDA about 3 years ago Actions #14

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

Updated by Marius BĂLTEANU about 3 years ago Actions #15

C S wrote in #note-13:

There are any news?

Only those from #39437.

Updated by Marius BĂLTEANU almost 3 years ago Actions #16

  • 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

Also available in: PDF Atom