DPDK patches and discussions
 help / color / mirror / Atom feed
From: Brandon Lo <blo@iol.unh.edu>
To: Aaron Conole <aconole@redhat.com>
Cc: "Zawadzki, Tomasz" <tomasz.zawadzki@intel.com>,
	Lincoln Lavoie <lylavoie@iol.unh.edu>,
	 "dpdklab@iol.unh.edu" <dpdklab@iol.unh.edu>,
	"ci@dpdk.org" <ci@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>,
	"spdk@lists.01.org" <spdk@lists.01.org>
Subject: Re: [dpdk-dev] [dpdklab] Re: [dpdk-ci] [CI] SPDK compilation failures @ DPDK community lab
Date: Tue, 9 Feb 2021 11:07:09 -0500	[thread overview]
Message-ID: <CAOeXdva_KdVOqmVTWaECKTRRgWpXjX+_RuT6d5vFB5FGy3DhCw@mail.gmail.com> (raw)
In-Reply-To: <f7th7ml5l6o.fsf@dhcp-25.97.bos.redhat.com>

Hi everyone,

I will adjust the branches and watch over the first few pipelines to
make sure everything goes smoothly.

Thanks for the update,
Brandon

On Tue, Feb 9, 2021 at 10:13 AM Aaron Conole <aconole@redhat.com> wrote:
>
> "Zawadzki, Tomasz" <tomasz.zawadzki@intel.com> writes:
>
> > Hi Lincoln,
> >
> >
> >
> > That patch in question is now merged to branch v21.01.x.
> >
>
> Good to know - I do still see a failure in the IOL job (even from a few
> hours ago).  I suppose the lab side might need some adjustment, too?
>
> >
> > The builds performed for latest SPDK and SPDK LTS, against dpdk-main branch seem to be passing. Would love to hear if
> > this is what you are seeing on your end too.
> >
> >
> >
> > Thanks,
> >
> > Tomek
> >
> >
> >
> > From: Lincoln Lavoie <lylavoie@iol.unh.edu>
> > Sent: Monday, February 8, 2021 5:21 PM
> > To: Zawadzki, Tomasz <tomasz.zawadzki@intel.com>
> > Cc: Aaron Conole <aconole@redhat.com>; Brandon Lo <blo@iol.unh.edu>; dpdklab@iol.unh.edu; ci@dpdk.org;
> > dev@dpdk.org; spdk@lists.01.org
> > Subject: Re: [dpdk-ci] [dpdk-dev] [CI] SPDK compilation failures @ DPDK community lab
> >
> >
> >
> > Thanks Tomek,
> >
> >
> >
> > Can you let us know when the merge happens and we'll make sure the next set of builds pass or see what the next failure
> > is. :-P
> >
> >
> >
> > Cheers,
> > Lincoln
> >
> >
> >
> > On Mon, Feb 8, 2021 at 11:03 AM Zawadzki, Tomasz <tomasz.zawadzki@intel.com> wrote:
> >
> >  Hi Aaron,
> >
> >  Thank you for reporting this !
> >
> >  This is an issue with rte_power now depending on rte_ethdev, which was resolved on latest SPDK.
> >
> >  I believe that UNH lab verifies DPDK patches against SPDK branch for latest release. Which after the very recent SPDK
> >  release, would be v21.01.x:
> >  https://github.com/spdk/spdk/tree/v21.01.x
> >
> >  The fix has been backported to that branch and should be merged shortly:
> >  https://review.spdk.io/gerrit/c/spdk/spdk/+/6320
> >
> >  Thanks,
> >  Tomek
> >
> >  > -----Original Message-----
> >  > From: dev <dev-bounces@dpdk.org> On Behalf Of Aaron Conole
> >  > Sent: Monday, February 8, 2021 4:21 PM
> >  > To: Brandon Lo <blo@iol.unh.edu>
> >  > Cc: dpdklab@iol.unh.edu; ci@dpdk.org; dev@dpdk.org; spdk@lists.01.org
> >  > Subject: [dpdk-dev] [CI] SPDK compilation failures @ DPDK community lab
> >  >
> >  > Greetings,
> >  >
> >  > I've noticed that recently SPDK compilation in the UNH community lab seems
> >  > to be failing, and I don't see an obvious reason for the failure.
> >  > The logs haven't been too helpful - it appears that there is a symbol that isn't
> >  > available when linking.
> >  >
> >  > Job details (for example):
> >  > https://lab.dpdk.org/results/dashboard/results/results-
> >  > uploads/test_runs/2363efb43157465db3228c34c00ebd57/log_upload_file/20
> >  > 21/2/dpdk_f6f2d2240153_15524_2021-02-04_22-59-59_NA.zip
> >  >
> >  > Is it possible to turn on more verbose logging during the compilation of
> >  > SPDK?  Maybe show the arguments to the compiler for the specific object?
> >  > Maybe the SPDK folks can see something obviously wrong?
> >  >
> >  > Thanks,
> >  > -Aaron
>


-- 

Brandon Lo

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

blo@iol.unh.edu

www.iol.unh.edu

  reply	other threads:[~2021-02-09 16:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08 15:21 [dpdk-dev] " Aaron Conole
2021-02-08 16:03 ` Zawadzki, Tomasz
2021-02-08 16:21   ` [dpdk-dev] [dpdk-ci] " Lincoln Lavoie
     [not found]     ` <DM6PR11MB422097059AB558056B97BEC5EE8F9@DM6PR11MB4220.namprd11.prod.outlook.com>
2021-02-09 15:13       ` Aaron Conole
2021-02-09 16:07         ` Brandon Lo [this message]
2021-02-09 17:54           ` [dpdk-dev] [dpdklab] " Brandon Lo
2021-02-11 14:02             ` Aaron Conole
2021-02-11 16:25               ` Brandon Lo
2021-02-12  9:18               ` Zawadzki, Tomasz
2021-02-12 17:39                 ` Brandon Lo
2021-02-15 15:28                   ` Aaron Conole
2021-02-17 16:06                     ` Zawadzki, Tomasz
2021-02-18 13:58                       ` Brandon Lo
2021-02-15  9:12                 ` [dpdk-dev] [SPDK] " David Marchand
2021-02-15  9:56                   ` Nick Connolly
2021-02-15 10:15                     ` 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=CAOeXdva_KdVOqmVTWaECKTRRgWpXjX+_RuT6d5vFB5FGy3DhCw@mail.gmail.com \
    --to=blo@iol.unh.edu \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    --cc=lylavoie@iol.unh.edu \
    --cc=spdk@lists.01.org \
    --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).