[
https://issues.apache.org/jira/browse/IGNITE-9726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16630561#comment-16630561
]
ASF GitHub Bot commented on IGNITE-9726:
----------------------------------------
GitHub user avplatonov opened a pull request:
https://github.com/apache/ignite/pull/4859
IGNITE-9726: GridCacheAbstractFailoverSelfTest may lock all suite on
put/remove cache operations
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9726
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4859.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4859
----
commit d02093c29d106b4ff4900ed7013d819880992e92
Author: Alexey Platonov <aplatonovv@...>
Date: 2018-09-27T14:46:22Z
fix suite lock due to missing of interruption in child threads
commit 40c3206752e2615603a85e0dbe56c2c0bc3266be
Author: Alexey Platonov <aplatonovv@...>
Date: 2018-09-27T14:46:34Z
Merge branch 'master' of https://github.com/apache/ignite into ignite-9726
----
> GridCacheAbstractFailoverSelfTest may lock all suite on put/remove cache
> operations
> -----------------------------------------------------------------------------------
>
> Key: IGNITE-9726
> URL: https://issues.apache.org/jira/browse/IGNITE-9726
> Project: Ignite
> Issue Type: Bug
> Reporter: Alexey Platonov
> Assignee: Alexey Platonov
> Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> Example of timeouts:
> [https://ci.ignite.apache.org/viewLog.html?buildId=1944646&buildTypeId=IgniteTests24Java8_CacheFailover2&tab=buildLog]
> method testConstantTopologyChange can misses interrupt from test runner and
> lock suite
> see that after thread dump put/remove cache operations will continue in test
> testOptimisticSerializableTxConstantTopologyChange
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
