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

Posted to issues@ignite.apache.org by "Ivan Pavlukhin (JIRA)" <ji...@apache.org> on 2019/04/26 18:39:00 UTC

[jira] [Commented] (IGNITE-11808) Scale test execution time constant along in IgniteCacheCrossCacheTxFailoverTest

    [ https://issues.apache.org/jira/browse/IGNITE-11808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827206#comment-16827206 ] 

Ivan Pavlukhin commented on IGNITE-11808:
-----------------------------------------

Run only touched test class on TC. Tests passed. Merged to master.

> Scale test execution time constant along in IgniteCacheCrossCacheTxFailoverTest
> -------------------------------------------------------------------------------
>
>                 Key: IGNITE-11808
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11808
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>            Reporter: Ivan Pavlukhin
>            Assignee: Ivan Pavlukhin
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Execution time of {{IgniteCacheCrossCacheTxFailoverTest}} is scaled by using {{ScaleFactorUtil}}. Currently an explicit constant is used to define test execution timeout and a magic constant is used after scaling to define a duration of the test. It is better to use the explicit constant throughout.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)