[jira] [Updated] (KUDU-1782) Fault injection tests should exit with a special exit code

["Todd Lipcon (JIRA)" <ji...@apache.org>]

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

Todd Lipcon updated KUDU-1782:
------------------------------
    Status: In Review  (was: Open)

> Fault injection tests should exit with a special exit code
> ----------------------------------------------------------
>
>                 Key: KUDU-1782
>                 URL: https://issues.apache.org/jira/browse/KUDU-1782
>             Project: Kudu
>          Issue Type: Improvement
>          Components: test
>    Affects Versions: 1.2.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>
> Currently, for the various fault injection crash points, we exit using LOG(FATAL). This has two issues:
> 1) we end up with a fair bit of log spew that isn't particularly useful, and which also confuses the "Diagnose" button on the flaky dashboard
> 2) our tests which are typically waiting for the server to crash can't distinguish the "expected" crash (injected fault) from any other crash (eg a bug that causes a SEGV or CHECK failure)
> To improve this, we can make the fault injection exit with some special error code, and have the tests that wait for the crash fail the test if they see a crash with another exit code (indicating SEGV or ABRT)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)