You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2023/03/03 07:58:00 UTC

[jira] [Updated] (IGNITE-18874) Add a JUnit extension for stopping all Ignites after test suite finishes

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

Roman Puchkovskiy updated IGNITE-18874:
---------------------------------------
    Description: It would be nice to have an automatically-registered extension that would stop all Ignite nodes started by a test suite (but which were not stopped for some reason). This might make our builds more stable decreasing the probability of a process hanging forever after a build, impeding other builds (as ports remain busy).

> Add a JUnit extension for stopping all Ignites after test suite finishes
> ------------------------------------------------------------------------
>
>                 Key: IGNITE-18874
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18874
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Roman Puchkovskiy
>            Assignee: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> It would be nice to have an automatically-registered extension that would stop all Ignite nodes started by a test suite (but which were not stopped for some reason). This might make our builds more stable decreasing the probability of a process hanging forever after a build, impeding other builds (as ports remain busy).



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