[
https://issues.apache.org/jira/browse/IGNITE-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16647732#comment-16647732
]
ASF GitHub Bot commented on IGNITE-8227:
----------------------------------------
GitHub user SomeFire opened a pull request:
https://github.com/apache/ignite/pull/4974
IGNITE-8227 test failure handler
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SomeFire/ignite IGNITE-8227
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4974.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 #4974
----
commit d4bc2199d6ebd72be328386ecadd0f900ad3b0a0
Author: Dmitrii Ryabov <somefireone@...>
Date: 2018-10-12T09:58:13Z
IGNITE-8227 test failure handler
----
> 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.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)
