Project

General

Profile

Actions
Copy link

Defect #19344

open

MySQL 5.6: IssueNestedSetConcurrencyTest#test_concurrency : always fails

Added by Rupesh J about 8 years ago. Updated over 1 year ago.

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

0%

Estimated time:
Resolution:
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 supportNew

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 subtasksReopenedJean-Philippe Lang

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 about 8 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 about 8 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 about 8 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 about 8 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 about 8 years ago

Actions
Copy link
 #6

Updated by Toshi MARUYAMA about 8 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 about 8 years ago

Actions
Copy link
 #8

Updated by Toshi MARUYAMA about 7 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 over 6 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 over 6 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 over 1 year 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 over 1 year 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

Also available in: Atom PDF