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

Reply via email to