You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2023/06/23 07:36:00 UTC

[jira] [Updated] (IGNITE-19815) Make ItTableScanTest resilient

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

Konstantin Orlov updated IGNITE-19815:
--------------------------------------
    Description: 
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.

  was:
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 on case of errors during scan.


> Make ItTableScanTest resilient 
> -------------------------------
>
>                 Key: IGNITE-19815
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19815
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Konstantin Orlov
>            Priority: Major
>              Labels: ignite-3
>
> 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)