[
https://issues.apache.org/jira/browse/IGNITE-10550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov updated IGNITE-10550:
--------------------------------------
Description:
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.
was:
Next tests failed in mvcc mode, most likely due to different MVCC tx semantic.
We have to create similar tests for mvcc mode.
IgniteWalFlushBackgroundSelfTest
IgniteWalFlushBackgroundWithMmapBufferSelfTest
IgniteWalFlushFsyncSelfTest
IgniteWalFlushFsyncWithDedicatedWorkerSelfTest
IgniteWalFlushFsyncWithMmapBufferSelfTest
IgniteWalFlushLogOnlySelfTest
IgniteWalFlushLogOnlyWithMmapBufferSelfTest
> MVCC: rework IgniteWalFlush* tests for mvcc.
> --------------------------------------------
>
> Key: IGNITE-10550
> URL: https://issues.apache.org/jira/browse/IGNITE-10550
> Project: Ignite
> Issue Type: Test
> Components: mvcc
> Reporter: Andrew Mashenkov
> Priority: Major
> Fix For: 2.8
>
>
> 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)
