[
https://issues.apache.org/jira/browse/IGNITE-10550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793743#comment-16793743
]
Andrew Mashenkov commented on IGNITE-10550:
-------------------------------------------
Tests passes locally, but fails on TC due to another reason: tx finish may
hangs after StorageException occurs.
Most likely, non-mvcc tests passes as non-mvcc transactions never persists
their states in TxLog or WAL.
> MVCC: rework IgniteWalFlush* tests for mvcc.
> --------------------------------------------
>
> Key: IGNITE-10550
> URL: https://issues.apache.org/jira/browse/IGNITE-10550
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
> Reporter: Andrew Mashenkov
> Assignee: Andrew Mashenkov
> Priority: Major
> Labels: WAL
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Next tests failed in mvcc mode, most likely due to different MVCC tx semantic:
> * IgniteWalFlushBackgroundSelfTest
> * IgniteWalFlushBackgroundWithMmapBufferSelfTest
> * IgniteWalFlushFsyncSelfTest
> * IgniteWalFlushFsyncWithDedicatedWorkerSelfTest
> * IgniteWalFlushFsyncWithMmapBufferSelfTest
> * IgniteWalFlushLogOnlySelfTest
> * IgniteWalFlushLogOnlyWithMmapBufferSelfTest
> We have to create similar tests for mvcc mode.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
