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

Diana Iakovleva reassigned IGNITE-11686:
----------------------------------------

    Assignee: Diana Iakovleva

> MVCC: Create separate test for vacuum checks.
> ---------------------------------------------
>
>                 Key: IGNITE-11686
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11686
>             Project: Ignite
>          Issue Type: Test
>          Components: mvcc
>            Reporter: Andrew Mashenkov
>            Assignee: Diana Iakovleva
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain, newbie
>
> Most of tests (inherited from CacheMvccAbstractTest) run vacuum synchronously 
> on afterTest() method and check if vacuum is ok. This hits performance, can 
> cause false negative results and
> vacuum issues can be hidden if afterTest method will overriden at once.
> For now we have CacheMvccVacuumTest that just check vacuum workers state, but 
> there is no check if vacuum really cleans all old versions correctly. I'd 
> expect to find it in this class.
> So, let's mode vacuum verification from afterTest method into 
> CacheMvccVacuumTest as a new separate test.
>  



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to