[
https://issues.apache.org/jira/browse/IGNITE-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16714751#comment-16714751
]
Dmitriy Pavlov commented on IGNITE-8227:
----------------------------------------
The original commit was reverted
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=87510597f5f21d8a2913a6c61334bf2fe546fc13
Dev list thread
https://lists.apache.org/thread.html/e0db80991af64f59d644e92369d9e8ee898a1e7a03dcdcc9ee071aaa@%3Cdev.ignite.apache.org%3E
> 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: Ryabov Dmitrii
> Priority: Major
>
> 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)
