[NXP-27660] Fix TestSQLRepositoryAPI.testLocking on MongoDB - Nuxeo Issue Tracker

XML

Word

Printable

Details

Type: Bug
Status: Resolved
Priority: Minor
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 11.1, 2021.0
Component/s: Core

Tags:
- nxplatform
- qaduty
Sprint:
nxplatform 11.1.15
Story Points:
2

Description

Since ~~NXP-24359~~, we can now lock twice a document without error.

The test TestSQLRepositoryAPI.testLocking has been updated to reflect this change but it has been failing on MongoDB since, see:

java.lang.AssertionError: expected:<org.nuxeo.ecm.core.api.Lock@6e009215> but was:<org.nuxeo.ecm.core.api.Lock@364a1b2f>
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failNotEquals(Assert.java:834)
	at org.junit.Assert.assertEquals(Assert.java:118)
	at org.junit.Assert.assertEquals(Assert.java:144)
	at org.nuxeo.ecm.core.TestSQLRepositoryAPI.testLocking(TestSQLRepositoryAPI.java:4369)

Issue is probably just the lack of equals implementation in Lock and it's not visible on VCS because VCSLockManager has a cache and so we get the same object.

Attachments

Issue Links

is caused by

NXP-24359 Document.Lock called twice should not fail

Resolved

Activity

People

Assignee:

Nour Al Kotob

Reporter:

Kevin Leturc

Participants:

Jenkins, Kevin Leturc, Nour Al Kotob

Votes:

0 Vote for this issue

Watchers:

2 Start watching this issue

Dates

Created:

2019-07-01 11:39

Updated:

2020-12-17 16:34

Resolved:

2019-08-08 08:39

Time Tracking

Estimated:

Not Specified

Remaining:

Logged: