[jira] [Closed] (IGNITE-207) Broken test:testOptimisticTxMissingKey* in full-API suite.

["Alexey Goncharuk (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Goncharuk closed IGNITE-207.
-----------------------------------

The issue was in test: in near only tests there was a possibility that txStart was called on one node, but actual puts were performed on the other node.

> Broken test:testOptimisticTxMissingKey* in full-API suite.
> ----------------------------------------------------------
>
>                 Key: IGNITE-207
>                 URL: https://issues.apache.org/jira/browse/IGNITE-207
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: sprint-1
>            Reporter: Vladimir Ozerov
>            Assignee: Alexey Goncharuk
>            Priority: Critical
>             Fix For: sprint-1
>
>
> Affected classes:
> GridCacheNearOnlyMultiNodeP2PDisabledFullApiSelfTest
> GridCacheReplicatedNearOnlyMultiNodeFullApiSelfTest
> Affected tests:
> testOptimisticTxMissingKey
> testOptimisticTxMissingKeyNoCommit
> What needs to be done:
> 1) Looks like testOptimisticTxMissingKeyNoCommit can be removed as it adds no value in addition to testOptimisticTxMissingKey.
> 2) Investigate failures. These two tests fail because we expect "true" for non-existing key removal in OPTIMISTIC tx, but in these two tests we receive "false". Returning "true" violates JCache semantics. Probably instead of fixing these two tests we must fix all other tests so that "false" is returned always.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)