DPDK CI discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>, tomasz.zawadzki@intel.com
Cc: dpdklab <dpdklab@iol.unh.edu>,
	Thomas Monjalon <thomas@monjalon.net>,
	ci@dpdk.org
Subject: Re: [dpdk-ci] SPDK compilation issue
Date: Tue, 17 Nov 2020 08:22:50 -0500	[thread overview]
Message-ID: <CAOE1vsNY=Y2gZ3pVMkRNC=JgaB_h3e+0Mzht-83dV+Yp0oe3Eg@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8y2yvA+tMNOEYM+2khcAA7rr8J0q61bJmy-Afy7J6FeHw@mail.gmail.com>

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

HI David,

Looping in Tomasz, who's been our primary contact on the SPDK side of
things.  I know Brandon just updated the SPDK test to pull from their
latest LTS release from October.

Cheers,
Lincoln

On Tue, Nov 17, 2020 at 2:35 AM David Marchand <david.marchand@redhat.com>
wrote:

> Hello,
>
> The SPDK job started failing following EAL changes.
>
> I proposed a fix to SPDK https://review.spdk.io/gerrit/c/spdk/spdk/+/5116.
> Not sure when it will be merged/fixed (first time submission for me).
>
> For now, I'll ignore failure reports for this job.
> If it gets too long to be fixed in SPDK, we might want to disable the job.
>
>
> --
> 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: 2260 bytes --]

  reply	other threads:[~2020-11-17 13:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17  7:35 David Marchand
2020-11-17 13:22 ` Lincoln Lavoie [this message]
2020-11-17 13:44   ` Zawadzki, Tomasz
2020-11-17 13:59     ` David Marchand
2020-11-18  8:36       ` Zawadzki, Tomasz
2020-11-18  9:32         ` David Marchand
2020-11-18 14:07           ` [dpdk-ci] [dpdklab] " Lincoln Lavoie
2020-11-18 15:56             ` Brandon Lo
2020-11-18 18:26               ` David Marchand
2020-11-18 18:36                 ` David Marchand
2020-11-19  8:37                   ` David Marchand
2020-11-24 11:05                     ` David Marchand

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='CAOE1vsNY=Y2gZ3pVMkRNC=JgaB_h3e+0Mzht-83dV+Yp0oe3Eg@mail.gmail.com' \
    --to=lylavoie@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dpdklab@iol.unh.edu \
    --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).