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

Dmitriy Pavlov updated IGNITE-8227:
-----------------------------------
    Description: 
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.

  was:
After IEP-14 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.


> 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)

Reply via email to