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

[jira] [Updated] (IGNITE-9896) TxRollbackOnTimeoutNoDeadlockDetectionTest fails in master for many tests

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

Alexei Scherbakov updated IGNITE-9896:
--------------------------------------
    Description: 
Example of 100% failing test:

org.apache.ignite.internal.processors.cache.transactions.TxRollbackOnTimeoutNoDeadlockDetectionTest#testRollbackOnTimeoutTxServerRemapPessimisticReadCommitted

This have not been noticed earlier because org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager#DEADLOCK_MAX_ITERS is static and propery is not correctly applied if test is executed from suite.

  was:
Example of 100% failing test:

org.apache.ignite.internal.processors.cache.transactions.TxRollbackOnTimeoutNoDeadlockDetectionTest#testRollbackOnTimeoutTxServerRemapPessimisticReadCommitted


> TxRollbackOnTimeoutNoDeadlockDetectionTest fails in master for many tests
> -------------------------------------------------------------------------
>
>                 Key: IGNITE-9896
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9896
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Alexei Scherbakov
>            Priority: Major
>             Fix For: 2.8
>
>
> Example of 100% failing test:
> org.apache.ignite.internal.processors.cache.transactions.TxRollbackOnTimeoutNoDeadlockDetectionTest#testRollbackOnTimeoutTxServerRemapPessimisticReadCommitted
> This have not been noticed earlier because org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager#DEADLOCK_MAX_ITERS is static and propery is not correctly applied if test is executed from suite.



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