[
https://issues.apache.org/jira/browse/IGNITE-6538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483715#comment-16483715
]
ASF GitHub Bot commented on IGNITE-6538:
----------------------------------------
GitHub user Mmuzaf opened a pull request:
https://github.com/apache/ignite/pull/4044
IGNITE-6538: run 200 times
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Mmuzaf/ignite ignite-6538
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4044.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 #4044
----
commit d37470c7a4c76e11aca60adc06d9ff4a4584aa28
Author: Maxim Muzafarov <maxmuzaf@...>
Date: 2018-04-22T14:00:01Z
IGNITE-6538: run 200 times
----
> Ignite Activate/Deactivate Cluster suite: After tests validation improvements
> test became flaky on TC
> -----------------------------------------------------------------------------------------------------
>
> Key: IGNITE-6538
> URL: https://issues.apache.org/jira/browse/IGNITE-6538
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Affects Versions: 2.1
> Reporter: Dmitriy Pavlov
> Assignee: Maxim Muzafarov
> Priority: Major
> Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.6
>
>
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&testNameId=-238119157387028099&tab=testDetails&branch_Ignite20Tests=%3Cdefault%3E
> recent changes from [IGNITE-6124] which probably showed this problem is
> following
> {noformat}
> fail("Activation should fail");
> {noformat}
> org.apache.ignite.internal.processors.cache.persistence.standbycluster.IgniteChangeGlobalStateTest#testActivateAfterFailGetLock
> Locally fail can be also reproduced, 6 from 20 failures.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
