From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: Brandon Lo <blo@iol.unh.edu>, dpdklab <dpdklab@iol.unh.edu>,
ci@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
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 08:52:42 -0400 [thread overview]
Message-ID: <CAOE1vsP=ZCOzv_xL5L05N4M2qBQbLbKjE99Mfs9XvoycGG8vGA@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8xTmp+BmZKkZ0vDWGEi9LgMD6ZNn3W5Lym_Hp2ZgMTw3w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2263 bytes --]
Hi David,
I disabled that pipeline, Brandon is looking into it this morning.
Something failed with starting the container, so they are definitely not
"real" failures.
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.
Cheers,
Lincoln
On Tue, Oct 6, 2020 at 5:51 AM David Marchand <david.marchand@redhat.com>
wrote:
> On Fri, Oct 2, 2020 at 6:44 PM David Marchand <david.marchand@redhat.com>
> wrote:
> >
> > On Fri, Oct 2, 2020 at 8:51 AM David Marchand <david.marchand@redhat.com>
> wrote:
> > >
> > > On Thu, Oct 1, 2020 at 8:24 PM Brandon Lo <blo@iol.unh.edu> wrote:
> > > > We have successfully added Fedora Rawhide to our production pipeline
> > > > for Meson compile testing.
> > > > The image for the container will be updated on a weekly basis.
> > > >
> > > > The version of GCC that it is currently running (10.2) catches that
> > > > the drivers/vdpa/ifc/base/ifcvf.h file redefines
> > > > VIRTIO_F_IOMMU_PLATFORM, originally from
> > > > /usr/include/linux/virtio_config.h.
> > > > I am just giving you guys a heads-up before the failure report
> catches
> > > > anyone off guard.
> > >
> > > Brandon,
> > >
> > > Before putting this new job online, the build issue should have been
> > > fixed on the dpdk side.
> > > All new submitted series are now getting a fail flag that we must
> > > inspect to check whether it is because of this known issue or
> > > something else.
> > >
> > > Please, disable this job.
> >
> > The vdpa/ifc issue should be fixed in the main branch now (thanks to
> Maxime).
> > But next-net and other subtrees will still have the issue until they
> > catch on this fix.
> >
> >
> > >
> > > There is also the OpenSuse job failing.
> > > Can you investigate?
> >
> > Still failing.
>
> I do not see failures for the OpenSuse job anymore, but since I got no
> reply, pinging again to get a clear status on this.
> Thanks.
>
>
> --
> David Marchand
>
>
--
*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: 4182 bytes --]
next prev parent reply other threads:[~2020-10-06 12:53 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 ` Lincoln Lavoie [this message]
2020-10-06 13:03 ` [dpdk-ci] [dpdklab] " Thomas Monjalon
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='CAOE1vsP=ZCOzv_xL5L05N4M2qBQbLbKjE99Mfs9XvoycGG8vGA@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
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).