This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: RFC V3 [1/2] test-in-container

From: Florian Weimer <fweimer at redhat dot com>
To: DJ Delorie <dj at redhat dot com>
Cc: libc-alpha at sourceware dot org
Date: Fri, 29 Jun 2018 07:01:01 +0200
Subject: Re: RFC V3 [1/2] test-in-container
References: <xnin62hb6v.fsf@greed.delorie.com>

On 06/28/2018 11:07 PM, DJ Delorie wrote:

Are there good guidelines for dealing with failures in the test harness
itself, rather than errors resulting from the actual thing being tested?
Or do we lump them all as "fail" and let the developers sort it out?

We treat it as FAIL if we cannot attribute it to a valid, expectedenvironmental limitation (such as a kernel which is too old, but stillsupported). I don't think there is any other way to do this.


Thanks,
Florian

References:
- Re: RFC V3 [1/2] test-in-container
  - From: DJ Delorie

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]