[ https://issues.apache.org/jira/browse/IGNITE-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16710311#comment-16710311 ]
ASF GitHub Bot commented on IGNITE-8227: ---------------------------------------- GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/5584 IGNITE-8227: Proper NoOpHandler injection. You can merge this pull request into a Git repository by running: $ git pull https://github.com/nizhikov/ignite IGNITE-8227-fix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5584.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5584 ---- commit 64842d77aa21feedebd634de4d2ed7ed1f6e4f8c Author: Nikolay Izhikov <nizhikov@...> Date: 2018-12-05T16:37:24Z IGNITE-8227: Proper NoOpHandler injection. ---- > 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 > Fix For: 2.8 > > > 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)