DPDK CI discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: David Marchand <david.marchand@redhat.com>,
	Brandon Lo <blo@iol.unh.edu>, dpdklab <dpdklab@iol.unh.edu>,
	ci@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
	Trishan de Lanerolle <tdelanerolle@linuxfoundation.org>,
	James Hendergart <j.hendergart@f5.com>
Subject: Re: [dpdk-ci] [dpdklab] Re: Fedora Rawhide Meson Compile Testing - DPDK Compile Warning
Date: Tue, 06 Oct 2020 15:03:47 +0200	[thread overview]
Message-ID: <4539298.X23b7sF8FS@thomas> (raw)
In-Reply-To: <CAOE1vsP=ZCOzv_xL5L05N4M2qBQbLbKjE99Mfs9XvoycGG8vGA@mail.gmail.com>

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



  reply	other threads:[~2020-10-06 13:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01 18:23 [dpdk-ci] " Brandon Lo
2020-10-02  6:51 ` David Marchand
2020-10-02 16:44   ` David Marchand
2020-10-06  9:50     ` David Marchand
2020-10-06 12:52       ` [dpdk-ci] [dpdklab] " Lincoln Lavoie
2020-10-06 13:03         ` Thomas Monjalon [this message]
2020-10-06 13:22           ` Lincoln Lavoie
2020-10-06 13:30             ` Thomas Monjalon
2020-10-06 14:07           ` Brandon Lo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4539298.X23b7sF8FS@thomas \
    --to=thomas@monjalon.net \
    --cc=blo@iol.unh.edu \
    --cc=bruce.richardson@intel.com \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dpdklab@iol.unh.edu \
    --cc=j.hendergart@f5.com \
    --cc=lylavoie@iol.unh.edu \
    --cc=tdelanerolle@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).