[infinispan-issues] [JBoss JIRA] (ISPN-2744) Random failure in VersionedConditionalOperationsTest.testRemoveIfPresent

[Dan Berindei (JIRA)]

Dan Berindei created ISPN-2744:
----------------------------------

             Summary: Random failure in VersionedConditionalOperationsTest.testRemoveIfPresent
                 Key: ISPN-2744
                 URL: https://issues.jboss.org/browse/ISPN-2744
             Project: Infinispan
          Issue Type: Bug
          Components: Test Suite
    Affects Versions: 5.2.0.CR2
            Reporter: Dan Berindei
            Assignee: Galder Zamarreño
             Fix For: 6.0.0.Final


The test does 2 sequential put operations from different nodes (1st put from node A, 2nd put from node B) and then checks that the last put value appears in both nodes.

However, the cache is configured with async commit phase, so the 1st tx's commit command can be executed on node B after the 2nd tx was already committed there:

{noformat}
00:32:01,165 TRACE (testng-VersionedConditionalOperationsTest:___defaultcache) [EntryWrappingInterceptor] About to commit entry ClusteredRepeatableReadEntry(66b3cb0){key=key_1, value=value_1, oldValue=null, isCreated=true, isChanged=true, isRemoved=false, isValid=true}
00:32:01,191 TRACE (testng-VersionedConditionalOperationsTest:___defaultcache) [EntryWrappingInterceptor] About to commit entry ClusteredRepeatableReadEntry(1af81e1){key=key_1, value=value_2, oldValue=null, isCreated=true, isChanged=true, isRemoved=false, isValid=true}
00:32:01,188 TRACE (OOB-1,ISPN,NodeB-21498:___defaultcache) [EntryWrappingInterceptor] About to commit entry ClusteredRepeatableReadEntry(7e2a710c){key=key_1, value=value_1, oldValue=null, isCreated=true, isChanged=true, isRemoved=false, isValid=true}
00:32:01,198 TRACE (OOB-2,ISPN,NodeA-27406:___defaultcache) [EntryWrappingInterceptor] About to commit entry ClusteredRepeatableReadEntry(61c63eff){key=key_1, value=value_2, oldValue=value_1, isCreated=false, isChanged=true, isRemoved=false, isValid=true}
{noformat}

The test should either use sync commit, or it should avoid checking consistency after a scenario like this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira