[
https://issues.jboss.org/browse/ISPN-3320?page=com.atlassian.jira.plugin....
]
Pedro Ruivo commented on ISPN-3320:
-----------------------------------
All the tests have failed due to the following scenario:
node1: performs a remote get
node2 (backup owner): receives and replies to the remote get with v1
node1: receives the repli and store in L1_ key => v1
node2 (backup owner): commits a new value (v2) for the key (i.e. processes a commit
command)
node3 (primary owner): sends the invalidation (but not for node1 because it hasn't
received the remote get yet) and commits a new value (v2) for the key (i.e. processes a
commit command)
node3 (primary owner): replies to the remote get with v2
node1: ignores the reply because it used the node2 reply
result: node1 keeps the old value stored in L1.
DistL1WriteSkewTest.testRemoveIgnoreReturnValueOnNonExistingKey fails
randomly
------------------------------------------------------------------------------
Key: ISPN-3320
URL:
https://issues.jboss.org/browse/ISPN-3320
Project: Infinispan
Issue Type: Bug
Reporter: Pedro Ruivo
Assignee: Pedro Ruivo
Fix For: 6.0.0.Alpha3
Attachments: logs.tar.gz
http://ci.infinispan.org/viewLog.html?buildId=2456&tab=buildResultsDi...
probably due to my last changes in write skew check...
failing tests:
* DistL1WriteSkewTest.testPutIgnoreReturnValueOnNonExistingKey
* DistL1WriteSkewTest.testRemoveIgnoreReturnValueNonExistingKey
* DistL1WriteSkewTest.testRemoveIgnoreReturnValueOnNonExistingKey
--
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