Hi Thomas,

For Rawhide, the failure is fixed, but I don't think it's ported to all branches yet, so how would you want to handle that.  Those branches will catch up and the failure would "disappear."

For GCC 11, that's bleeding edge, so it's more about future proofing and how that plan is put together.

Cheers,
Lincoln

On Tue, Oct 6, 2020 at 9:03 AM Thomas Monjalon <thomas@monjalon.net> wrote:
06/10/2020 14:52, Lincoln Lavoie:
> For Rawhide, our plan is to mark the failures as warnings instead, until
> things catch up on the other branches.  Similarly, if we add something like
> GCC 11 compile, I would suggest those failures are also a warning for now.

Sorry, I disagree with this plan.
As a non-regression tool, we are looking for green lights.
If a new test is not passing, it should not be added
until the original issue is fixed.

Please don't add tests if they are failing, giving warning or error.

Thanks




--
Lincoln Lavoie
Senior Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
+1-603-674-2755 (m)