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

Posted to issues@ignite.apache.org by "Andrey Gura (JIRA)" <ji...@apache.org> on 2018/04/12 10:24:00 UTC

[jira] [Commented] (IGNITE-8227) Research possibility and implement JUnit test failure handler for TeamCity

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

Andrey Gura commented on IGNITE-8227:
-------------------------------------

It's adhook decision and should be made by developer during test development. I have doubt that some common failure handler makes sense.

> Research possibility and implement JUnit test failure handler for TeamCity
> --------------------------------------------------------------------------
>
>                 Key: IGNITE-8227
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8227
>             Project: Ignite
>          Issue Type: Test
>            Reporter: Dmitriy Pavlov
>            Assignee: Dmitriy Pavlov
>            Priority: Major
>             Fix For: 2.6
>
>
> After IEP-14 (https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling)  we found a lot of TC failures involving unexpected nodes stop.
> To avoid suites exit codes, tests have NoOpFailureHandler as default.
> But instead of this, better handler could be 
> stopNode + fail currenly running test with message.
> This default allows to identify such failures without log-message fail condition.



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