From: David Marchand <david.marchand@redhat.com>
To: Brandon Lo <blo@iol.unh.edu>
Cc: ci@dpdk.org, "Zawadzki, Tomasz" <tomasz.zawadzki@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-ci] SPDK Failures
Date: Thu, 18 Mar 2021 16:44:25 +0100 [thread overview]
Message-ID: <CAJFAV8x3EspGm7s0EB4NBtw89piuTzi6B7GD5derM7iQA9CEhA@mail.gmail.com> (raw)
In-Reply-To: <CAOeXdvapWz1XJkCid3aK3hUPRrq4itdwbpH6LGys3ATPBzZe6g@mail.gmail.com>
Hello Brandon,
On Thu, Mar 18, 2021 at 4:36 PM Brandon Lo <blo@iol.unh.edu> wrote:
>
> Hi all,
>
> We have noticed some SPDK failures come through to the lab.
> I have looked into the errors; it seems like it has an issue with
> building SPDK itself:
The problem is on the dpdk side.
I reported yesterday:
http://inbox.dpdk.org/dev/CAJFAV8zg-TNcMWwMhQW6cC-7MU+bSKQPoHFgastBn1N+HbEaZQ@mail.gmail.com/
The fix is in the main branch:
https://git.dpdk.org/dpdk/commit/?id=643752207964b2abd0863d9b3dc7522a40469ba0
--
David Marchand
prev parent reply other threads:[~2021-03-18 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 15:36 Brandon Lo
2021-03-18 15: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=CAJFAV8x3EspGm7s0EB4NBtw89piuTzi6B7GD5derM7iQA9CEhA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=blo@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=thomas@monjalon.net \
--cc=tomasz.zawadzki@intel.com \
/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).