You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/04/22 14:02:00 UTC

[jira] [Commented] (IGNITE-6538) Ignite Activate/Deactivate Cluster suite: After tests validation improvements test became flaky on TC

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

ASF GitHub Bot commented on IGNITE-6538:
----------------------------------------

GitHub user Mmuzaf opened a pull request:

    https://github.com/apache/ignite/pull/3897

    IGNITE-6538: test 500 times

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Mmuzaf/ignite check-ignite-6538

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/3897.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 #3897
    
----
commit 5496341a7ccca6edb553af6f4ee4e2f8859ce015
Author: Maxim Muzafarov <ma...@...>
Date:   2018-04-22T14:00:01Z

    IGNITE-6538: test 500 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
>            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)