DPDK CI discussions
 help / color / mirror / Atom feed
From: Brandon Lo <blo@iol.unh.edu>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Lincoln Lavoie <lylavoie@iol.unh.edu>,
	David Marchand <david.marchand@redhat.com>,
	 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 10:07:23 -0400
Message-ID: <CAOeXdvauO-r-kOt-aHyh185t3X-_m1tCp7k+Fpf_3ffvN2r=hQ@mail.gmail.com> (raw)
In-Reply-To: <4539298.X23b7sF8FS@thomas>

Hi everyone,

Apologies for the issues this has caused. I have since added the
ability to store warning results on the dashboard.
I will be resending the result emails.

I have also fixed OpenSUSE builds and will be rerunning tests
throughout the day.


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


Brandon Lo

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824



      parent reply	other threads:[~2020-10-06 14:08 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
2020-10-06 13:30             ` Thomas Monjalon
2020-10-06 14:07           ` Brandon Lo [this message]

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:

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

  git send-email \
    --in-reply-to='CAOeXdvauO-r-kOt-aHyh185t3X-_m1tCp7k+Fpf_3ffvN2r=hQ@mail.gmail.com' \
    --to=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 \
    --cc=thomas@monjalon.net \


* 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 \
	public-inbox-index ci

Example config snippet for mirrors.
Newsgroup available over NNTP:

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