[dpdk-ci] [dpdklab] Re: Fedora Rawhide Meson Compile Testing - DPDK Compile Warning

Thomas Monjalon thomas at monjalon.net
Tue Oct 6 15:30:35 CEST 2020


06/10/2020 15:22, Lincoln Lavoie:
> On Tue, Oct 6, 2020 at 9:03 AM Thomas Monjalon <thomas at 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.
> 
> 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."

Yes it will disappear, nothing to do on the lab side.

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

I propose you prepare the test, run once and send the report
to dev and ci mailing lists.
Then when we (maintainers) consider it should be fixed,
we will ask you to test again.
If the issue is fixed, you can add the test in the CI.

Would it work?




More information about the ci mailing list