DPDK CI discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: Thomas Monjalon <thomas@monjalon.net>
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, 6 Oct 2020 09:22:27 -0400
Message-ID: <CAOE1vsP_+aY3G0qjwU5RwkWOexSOUpm0kyPgDsqrD9cxM-=b+w@mail.gmail.com> (raw)
In-Reply-To: <4539298.X23b7sF8FS@thomas>

[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]

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
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu>

[-- Attachment #2: Type: text/html, Size: 2600 bytes --]

  reply	other threads:[~2020-10-06 13:23 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
2020-10-06 13:22           ` Lincoln Lavoie [this message]
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='CAOE1vsP_+aY3G0qjwU5RwkWOexSOUpm0kyPgDsqrD9cxM-=b+w@mail.gmail.com' \
    --to=lylavoie@iol.unh.edu \
    --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=tdelanerolle@linuxfoundation.org \
    --cc=thomas@monjalon.net \
    /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

DPDK CI discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git