This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Do we care about malloc failure in tests?
- From: DJ Delorie <dj at redhat dot com>
- To: Paul Pluzhnikov <ppluzhnikov at google dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Tue, 31 May 2016 15:02:29 -0400
- Subject: Re: Do we care about malloc failure in tests?
- Authentication-results: sourceware.org; auth=none
- References: <CALoOobNcJ6MaE3OfhY2KebXa=Z8kzhsgKpoesbzvvhUEEZhz=A at mail dot gmail dot com>
If a test fails due to out-of-memory, do we have a way of noting that
the failure was for a cause unrelated to what the test was testing?
I mean, if we're testing fopen() and we run out of memory, that doesn't
mean that fopen() is broken or that something in glibc needs to be
fixed, it just means that that test wasn't completed.