This is the mail archive of the
mailing list for the glibc project.
Re: Do we care about malloc failure in tests?
- From: Roland McGrath <roland at hack dot frob dot com>
- To: DJ Delorie <dj at redhat dot com>
- Cc: Paul Pluzhnikov <ppluzhnikov at google dot com>, libc-alpha at sourceware dot org
- Date: Tue, 31 May 2016 12:09:52 -0700 (PDT)
- 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> <xnlh2q1262 dot fsf at greed dot delorie dot com>
We have exit(77) to yield UNSUPPORTED. But IMHO using that for cases like
malloc failure is worse than FAIL. We could add another test outcome for
such badness, but I don't see any urgency in doing any such thing. If
tests fail due to such an issue, you'll look at what went wrong, be
confused, and try running the tests again, when they'll work.