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

Konstantin Orlov updated IGNITE-19815:
--------------------------------------
    Fix Version/s: 3.0.0-beta2

> Make ItTableScanTest resilient 
> -------------------------------
>
>                 Key: IGNITE-19815
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19815
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Konstantin Orlov
>            Assignee: Konstantin Orlov
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> After IGNITE-17951 a few tests (namely ItTableScanTest and 
> ItInternalTableReadWriteScanTest) were switched to a new scan method 
> accepting tx id only. The difference between old method and new method is 
> that latter lack the tx finalisation step in case of any error. This causes 
> cascade failures of tests within the same class, since no one rollbacks the 
> tx manually.
> To make tests more resilient to cascade failures, let's restore the logic for 
> tx finalisation in case of errors during scan.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to