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.
Attachments
Issue Links
- is blocked by
-
IGNITE-11559 MVCC: Tx hangs on finish if StorageException occurs.
- Resolved
- requires
-
IGNITE-11587 MVCC: Remote tx determine its type in wrong way.
- Resolved
- links to