You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2020/02/14 00:06:00 UTC

[jira] [Commented] (IGNITE-12667) Flaky test FailureProcessorThreadDumpThrottlingTest.testThrottlingPerFailureType

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

Ignite TC Bot commented on IGNITE-12667:
----------------------------------------

{panel:title=Branch: [pull/7415/head] Base: [master] : Possible Blockers (1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}MVCC Cache 7{color} [[tests 0 TIMEOUT , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=5048652]]

{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=5044169&amp;buildTypeId=IgniteTests24Java8_RunAll]

> Flaky test FailureProcessorThreadDumpThrottlingTest.testThrottlingPerFailureType
> --------------------------------------------------------------------------------
>
>                 Key: IGNITE-12667
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12667
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Andrey N. Gura
>            Assignee: Andrey N. Gura
>            Priority: Major
>             Fix For: 2.9
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Test {{FailureProcessorThreadDumpThrottlingTest#testThrottlingPerFailureType}} is flaky. On TC agents thread dumps generation takes a lot of time, so current throttling timeout is too small for TC.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)