ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitriy Pavlov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9376) Create table with critical failures
Date Tue, 11 Sep 2018 09:52:00 GMT

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

Dmitriy Pavlov commented on IGNITE-9376:
----------------------------------------

[~SomeFire] I have an idea why it is so, the reason of it - data of recent failures (And as
result, flaky detection) is based on PR branch instead of the base (master branch).
org/apache/ignite/ci/web/model/current/TestFailure.java:219

I will fix it or create an additional unassigned issue. I would like to think if there can
be some refactoring with there rates.

> Create table with critical failures
> -----------------------------------
>
>                 Key: IGNITE-9376
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9376
>             Project: Ignite
>          Issue Type: Sub-task
>            Reporter: Ryabov Dmitrii
>            Assignee: Ryabov Dmitrii
>            Priority: Major
>
> Create separate table for critical failures (suite timouts, suite non-zero exit codes,
etc) and new tests (failure rate 0.0%) on the PR analysis page of TCH.



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

Mime
View raw message