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

[jira] [Assigned] (IGNITE-9815) [TC Bot] Muted tests shouldn't considered as blocker

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

Ryabov Dmitrii reassigned IGNITE-9815:
--------------------------------------

    Assignee: Ryabov Dmitrii

> [TC Bot] Muted tests shouldn't considered as blocker
> ----------------------------------------------------
>
>                 Key: IGNITE-9815
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9815
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Nikolay Izhikov
>            Assignee: Ryabov Dmitrii
>            Priority: Major
>
> Currently, TC bot doesn't analyze stack trace of test fail [1].
> If some test failed with the link to Ignite ticket it shouldn't be considered as a blocker.
> Link with examples of such behaviour:
> {noformat}
> IgniteCacheMvccTestSuite: DataStreamProcessorMvccSelfTest.testColocated - 0,0% fails in last 100 master runs.
> IgniteCacheMvccTestSuite: DataStreamProcessorMvccSelfTest.testPartitioned - 0,0% fails in last 100 master runs.
> IgniteCacheMvccTestSuite: DataStreamProcessorMvccSelfTest.testReplicated - 0,0% fails in last 100 master runs.
> {noformat}
> stack trace:
> {noformat}
> unit.framework.AssertionFailedError: https://issues.apache.org/jira/browse/IGNITE-9722
>     at org.apache.ignite.internal.processors.cache.mvcc.CacheMvccTransactionsTest.testMvccCoordinatorChangeSimple(CacheMvccTransactionsTest.java:2387)
> {noformat}
> https://issues.apache.org/jira/browse/IGNITE-9272?focusedCommentId=16641617&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16641617



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