You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ivan Pavlukhin (JIRA)" <ji...@apache.org> on 2019/01/25 08:26:00 UTC

[jira] [Comment Edited] (IGNITE-10444) MVCC: CacheMvccTxFastFinishTest fails.

    [ https://issues.apache.org/jira/browse/IGNITE-10444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16751131#comment-16751131 ] 

Ivan Pavlukhin edited comment on IGNITE-10444 at 1/25/19 8:25 AM:
------------------------------------------------------------------

Checked that failure reproduces on https://github.com/apache/ignite/commit/4ea443ceffa4445003aa5c8448017eb430cedff3
From the first glance test in question checks prepare and finish futures at specific stages of transaction execution. Perhaps, difference in flows makes assertions invalid for MVCC transactions.


was (Author: pavlukhin):
Checked that failure reproduces on https://github.com/apache/ignite/commit/4ea443ceffa4445003aa5c8448017eb430cedff3

> MVCC: CacheMvccTxFastFinishTest fails.
> --------------------------------------
>
>                 Key: IGNITE-10444
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10444
>             Project: Ignite
>          Issue Type: Bug
>          Components: mvcc
>            Reporter: Andrew Mashenkov
>            Priority: Major
>
> Seems, read-only transaction doesn't creates prepare\finish future as classic tx do.
> Let's check correct invariants in  mvcc version of CacheTxFastFinishTest test.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)