Re: [PATCH] Fix exit status of signal handlers in shell scripts

[Jim Meyering]

Dmitry V. Levin wrote:
> On Sun, Jan 31, 2010 at 01:04:09AM +0100, Bruno Haible wrote:
...
>> For the tests, I am inclined to provide the exit
>> code '77' (= SKIP), rather than '1' (= FAIL): If a test is terminated
>> by Ctrl-C, it has neither passed nor failed.
>
> Yes, it makes sense.

Actually, letting a signal provoke non-failure could lead to confusion.
Imagine that the first 10 tests pass, then each of the remaining ones is
killed via e.g., SIGHUP.  The final result would be highly misleading:

    ========================
    All 10 tests passed
    (300 tests were not run)
    ========================

and a naive search for "FAIL:" in the build output would find nothing.
For those reasons, I think it's clear that such conditions must evoke
failure, and not "exit 77".