You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Oleg Ignatenko (JIRA)" <ji...@apache.org> on 2018/10/01 15:55:00 UTC

[jira] [Updated] (IGNITE-9754) Increase timeout waiting for commitLatch in test TxRollbackAsyncWithPersistenceTest.testRollbackOnTopologyLockPessimistic

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

Oleg Ignatenko updated IGNITE-9754:
-----------------------------------
    Labels: MakeTeamcityGreenAgain  (was: )

> Increase timeout waiting for commitLatch in test TxRollbackAsyncWithPersistenceTest.testRollbackOnTopologyLockPessimistic
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-9754
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9754
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.6
>            Reporter: Oleg Ignatenko
>            Assignee: Oleg Ignatenko
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>             Fix For: 2.8
>
>
> Current timeout for {{commitLatch}} in test {{TxRollbackAsyncWithPersistenceTest.testRollbackOnTopologyLockPessimistic}} is 10 seconds.
> This looks insufficient to make a compelling reason that test failure indicates a problem in the implementation. For example log of this [recent failure at Teamcity|https://ci.ignite.apache.org/viewLog.html?buildId=1970040&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Cache7] suggests that there were just a couple of non-critical delays for a few seconds that made test fail.
> Suggest to increase timeout from 10 seconds to 60, so that in case if test fails waiting on the latch one could assume with reasonable certainty that something is wrong with the implementation or infrastructure.



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