From: David Marchand <david.marchand@redhat.com>
To: Brandon Lo <blo@iol.unh.edu>, dpdklab@iol.unh.edu
Cc: ci@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [dpdk-ci] Fedora Rawhide Meson Compile Testing - DPDK Compile Warning
Date: Fri, 2 Oct 2020 18:44:34 +0200 [thread overview]
Message-ID: <CAJFAV8zr1cKE8kGvvwoVp5KqWs2+J3Aqif1DQ+4BZivFWC8=jg@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8yAeuCG68y5HKN5QLUZOs+8A2d_+hA__WY=M1bzoBe32w@mail.gmail.com>
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.
--
David Marchand
prev parent reply other threads:[~2020-10-02 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOeXdvatG8S20KgQuRaqGG_6aDNLGrgzg1W=f0Ps2c4BRFWUxg@mail.gmail.com>
2020-10-02 6:51 ` David Marchand
2020-10-02 16:44 ` David Marchand [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:
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='CAJFAV8zr1cKE8kGvvwoVp5KqWs2+J3Aqif1DQ+4BZivFWC8=jg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=blo@iol.unh.edu \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--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).