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

Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2020/12/29 08:58:12 UTC

[jira] [Updated] (IGNITE-13438) Correction of error behavior in control.sh

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

Maxim Muzafarov updated IGNITE-13438:
-------------------------------------
    Fix Version/s:     (was: 2.10)

> Correction of error behavior in control.sh
> ------------------------------------------
>
>                 Key: IGNITE-13438
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13438
>             Project: Ignite
>          Issue Type: Improvement
>          Components: control.sh
>            Reporter: Kirill Tkalenko
>            Priority: Major
>
> # If the command fails, control.sh should not return EXIT_CODE_OK (an example of a violation is testClusterChangeTag);
> # In case of an error in the normal state (the cluster is inactive, it has already started for a year, etc.) stacktraces should not be printed;
> # Need to add specific general error codes so that you do not use EXIT_CODE_UNEXPECTED_ERROR in step 2.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)