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

Roman Puchkovskiy updated IGNITE-25149:
---------------------------------------
    Description: 
In many cases, failure processor is invoked by passing tests. This usually 
happens due to node being stopped and NodeStoppingException being thrown. But 
in some tests some background activities fail, so failure processor is 
triggered, but we don't 'see' it as the tests still pass (but maybe some 
internal cleanup is broken).

Here, [https://ci.ignite.apache.org/project/ApacheIgnite3xGradle_TestDevelop] a 
new rule is added that inspects logs remaining from a run. If it finds that 
failure processor was invoked, it fails the build.

The idea of this issue is to make builds pass even with this new rule. We must 
fix what we can fix while doing so; what we cannot fix, we should mute under 
the corresponding issues.

> Failure handler is triggered by passing tests
> ---------------------------------------------
>
>                 Key: IGNITE-25149
>                 URL: https://issues.apache.org/jira/browse/IGNITE-25149
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Roman Puchkovskiy
>            Assignee: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> In many cases, failure processor is invoked by passing tests. This usually 
> happens due to node being stopped and NodeStoppingException being thrown. But 
> in some tests some background activities fail, so failure processor is 
> triggered, but we don't 'see' it as the tests still pass (but maybe some 
> internal cleanup is broken).
> Here, [https://ci.ignite.apache.org/project/ApacheIgnite3xGradle_TestDevelop] 
> a new rule is added that inspects logs remaining from a run. If it finds that 
> failure processor was invoked, it fails the build.
> The idea of this issue is to make builds pass even with this new rule. We 
> must fix what we can fix while doing so; what we cannot fix, we should mute 
> under the corresponding issues.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to