Project

General

Profile

Actions
Copy link

Defect #5290

closed

r3664 breaks tests on SQLite3

Added by Holger Just about 15 years ago. Updated about 15 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-04-11
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

See http://ci.finn.de/builds/1-8-7_redmine-trunk_sqlite3/3664

Failure: test_put_update_stale_issue(IssuesControllerTest)
[/test/functional/issues_controller_test.rb:988:in `test_put_update_stale_issue'
 /test/functional/issues_controller_test.rb:987:in `test_put_update_stale_issue']: 

"TimeEntry.count" didn't change by 0.
<4> expected but was <5>.

The error does only occur on SQLite3. It passes on MySQL 5.0 and PostgreSQL 8.3.

It seems like SQLite3 does not properly follow the transaction and inserts the TimeEntry even though the transaction is later rolled back (I might be seriously wrong though...)

Actions
Copy link
 #1

Updated by Jean-Philippe Lang about 15 years ago

You're absolutely right. I'm aware of it.

Actions
Copy link
 #2

Updated by Jean-Philippe Lang about 15 years ago

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

The problem was due to transactional fixtures and was not occuring when running the application.
Anyway, it's fixed in r3669 by moving the test to a new class with transactional fixtures turned off.

Actions
Copy link

Also available in: Atom PDF