Project

General

Profile

Actions

Defect #7253

closed

Test failures in MercurialAdapterTest

Added by Jean-Philippe Lang over 13 years ago. Updated about 13 years ago.

Status:
Closed
Priority:
High
Assignee:
Toshi MARUYAMA
Category:
SCM
Target version:
-
Start date:
2011-01-09
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

With r4667 (trunk or 1.1-stable), I'm getting some test failures on MercurialAdapterTest. Mercurial version used for testing is 1.7.

When running tests under linux:

  1) Failure:
test_diff(MercurialAdapterTest)
    [/test/unit/lib/redmine/scm/adapters/mercurial_adapter_test.rb:54:in `test_diff'
     /test/unit/lib/redmine/scm/adapters/mercurial_adapter_test.rb:52:in `each'
     /test/unit/lib/redmine/scm/adapters/mercurial_adapter_test.rb:52:in `test_diff'
     /test/unit/lib/redmine/scm/adapters/mercurial_adapter_test.rb:48:in `each'
     /test/unit/lib/redmine/scm/adapters/mercurial_adapter_test.rb:48:in `test_diff']:
<50> expected but was
<49>.

When running tests under windows:

  1) Failure:
test_diff(MercurialAdapterTest)
    [test/unit/lib/redmine/scm/adapters/mercurial_adapter_test.rb:51:in `test_diff'
     test/unit/lib/redmine/scm/adapters/mercurial_adapter_test.rb:48:in `each'
     test/unit/lib/redmine/scm/adapters/mercurial_adapter_test.rb:48:in `test_diff']:
<"+    return true unless klass.respond_to?('watched_by')\r\n"> expected but was
<"+    return true unless klass.respond_to?('watched_by')\n">.

If I manually fix the assertion, I get other failure in the same test (test_diff).

Can you check that ? 1.1 release is planned today.


Related issues

Related to Redmine - Defect #7518: Mercurial diff can be wrong if the previous changeset isn't the parentClosedToshi MARUYAMA2011-02-02

Actions
Actions

Also available in: Atom PDF