[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] tests init: new subroutine 'fatal_', for hard errors
From: |
Eric Blake |
Subject: |
Re: [PATCH] tests init: new subroutine 'fatal_', for hard errors |
Date: |
Tue, 07 Jun 2011 14:33:02 -0600 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110428 Fedora/3.1.10-1.fc14 Lightning/1.0b3pre Mnenhy/0.8.3 Thunderbird/3.1.10 |
On 06/07/2011 02:22 PM, Bruno Haible wrote:
> Stefano Lattarini wrote:
>> +fatal_ () { warn_ "$ME_: hard error: $@"; Exit 99; }
>
> What is a "hard error"?
>
> I thought a test could either succeed, or fail, or produce no result due to
> unexpected circumstances, and this last case was called "framework failure".
> Quartum non datur.
>
> So, what is a "hard error"?
Exit status 99 is special to automake - it says quit the testsuite now,
regardless of how many tests remain, because this error is indicative of
something so seriously broken that many other tests will likely fail as
a knock-on effect of the bug exposed by this failure.
All other failure exit status let automake proceed on with the remainder
of the testsuite.
--
Eric Blake address@hidden +1-801-349-2682
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
- [PATCH] tests init: new subroutine 'fatal_', for hard errors, Stefano Lattarini, 2011/06/07
- Re: [PATCH] tests init: new subroutine 'fatal_', for hard errors, Eric Blake, 2011/06/07
- Re: [PATCH] tests init: new subroutine 'fatal_', for hard errors, Bruno Haible, 2011/06/07
- Re: [PATCH] tests init: new subroutine 'fatal_', for hard errors,
Eric Blake <=