All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: "Zawadzki\, Tomasz" <tomasz.zawadzki@intel.com>
Cc: Lincoln Lavoie <lylavoie@iol.unh.edu>,
	Brandon Lo <blo@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] [dpdk-ci] [CI] SPDK compilation failures @ DPDK community lab
Date: Tue, 09 Feb 2021 10:13:03 -0500	[thread overview]
Message-ID: <f7th7ml5l6o.fsf@dhcp-25.97.bos.redhat.com> (raw)
In-Reply-To: <DM6PR11MB422097059AB558056B97BEC5EE8F9@DM6PR11MB4220.namprd11.prod.outlook.com> (Tomasz Zawadzki's message of "Mon, 8 Feb 2021 17:17:34 +0000")

"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


WARNING: multiple messages have this Message-ID (diff)
From: Aaron Conole <aconole at redhat.com>
To: spdk@lists.01.org
Subject: [SPDK] Re: [dpdk-ci] [dpdk-dev] [CI] SPDK compilation failures @ DPDK community lab
Date: Tue, 09 Feb 2021 15:13:14 +0000	[thread overview]
Message-ID: <f7th7ml5l6o.fsf@dhcp-25.97.bos.redhat.com> (raw)
In-Reply-To: DM6PR11MB422097059AB558056B97BEC5EE8F9@DM6PR11MB4220.namprd11.prod.outlook.com

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

"Zawadzki, Tomasz" <tomasz.zawadzki(a)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(a)iol.unh.edu> 
> Sent: Monday, February 8, 2021 5:21 PM
> To: Zawadzki, Tomasz <tomasz.zawadzki(a)intel.com>
> Cc: Aaron Conole <aconole(a)redhat.com>; Brandon Lo <blo(a)iol.unh.edu>; dpdklab(a)iol.unh.edu; ci(a)dpdk.org;
> dev(a)dpdk.org; spdk(a)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(a)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(a)dpdk.org> On Behalf Of Aaron Conole
>  > Sent: Monday, February 8, 2021 4:21 PM
>  > To: Brandon Lo <blo(a)iol.unh.edu>
>  > Cc: dpdklab(a)iol.unh.edu; ci(a)dpdk.org; dev(a)dpdk.org; spdk(a)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

  reply	other threads:[~2021-02-09 15:13 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08 15:21 [dpdk-dev] [CI] SPDK compilation failures @ DPDK community lab Aaron Conole
2021-02-08 15:21 ` [SPDK] " Aaron Conole
2021-02-08 16:03 ` [dpdk-dev] " Zawadzki, Tomasz
2021-02-08 16:03   ` [SPDK] " Zawadzki, Tomasz
2021-02-08 16:21   ` [dpdk-dev] [dpdk-ci] " Lincoln Lavoie
2021-02-08 16:21     ` [SPDK] Re: [dpdk-ci] [dpdk-dev] " Lincoln Lavoie
2021-02-08 17:17     ` Zawadzki, Tomasz
2021-02-09 15:13       ` Aaron Conole [this message]
2021-02-09 15:13         ` Aaron Conole
2021-02-09 16:07         ` [dpdk-dev] [dpdklab] Re: [dpdk-ci] " Brandon Lo
2021-02-09 16:07           ` [SPDK] Re: [dpdklab] Re: [dpdk-ci] [dpdk-dev] " Brandon Lo
2021-02-09 17:54           ` [dpdk-dev] [dpdklab] Re: [dpdk-ci] " Brandon Lo
2021-02-09 17:55             ` [SPDK] Re: [dpdklab] Re: [dpdk-ci] [dpdk-dev] " Brandon Lo
2021-02-11 14:02             ` [dpdk-dev] [dpdklab] Re: [dpdk-ci] " Aaron Conole
2021-02-11 14:02               ` [SPDK] Re: [dpdklab] Re: [dpdk-ci] [dpdk-dev] " Aaron Conole
2021-02-11 16:25               ` [dpdk-dev] [dpdklab] Re: [dpdk-ci] " Brandon Lo
2021-02-11 16:25                 ` [SPDK] Re: [dpdklab] Re: [dpdk-ci] [dpdk-dev] " Brandon Lo
2021-02-12  9:18               ` [dpdk-dev] [dpdklab] Re: [dpdk-ci] " Zawadzki, Tomasz
2021-02-12  9:18                 ` [SPDK] Re: [dpdklab] Re: [dpdk-ci] [dpdk-dev] " Zawadzki, Tomasz
2021-02-12 17:39                 ` [dpdk-dev] [dpdklab] Re: [dpdk-ci] " Brandon Lo
2021-02-12 17:40                   ` [SPDK] Re: [dpdklab] Re: [dpdk-ci] [dpdk-dev] " Brandon Lo
2021-02-15 15:28                   ` [dpdk-dev] [dpdklab] Re: [dpdk-ci] " Aaron Conole
2021-02-15 15:28                     ` [SPDK] Re: [dpdklab] Re: [dpdk-ci] [dpdk-dev] " Aaron Conole
2021-02-17 16:06                     ` [dpdk-dev] [dpdklab] Re: [dpdk-ci] " Zawadzki, Tomasz
2021-02-17 16:06                       ` [SPDK] Re: [dpdklab] Re: [dpdk-ci] [dpdk-dev] " Zawadzki, Tomasz
2021-02-18 13:58                       ` [dpdk-dev] [dpdklab] Re: [dpdk-ci] " Brandon Lo
2021-02-18 13:58                         ` [SPDK] Re: [dpdklab] Re: [dpdk-ci] [dpdk-dev] " Brandon Lo
2021-02-15  9:12                 ` [dpdk-dev] [SPDK] Re: [dpdklab] Re: [dpdk-ci] " David Marchand
2021-02-15  9:12                   ` [SPDK] Re: [dpdklab] Re: [dpdk-ci] [dpdk-dev] " David Marchand
2021-02-15  9:56                   ` [dpdk-dev] [SPDK] Re: [dpdklab] Re: [dpdk-ci] " Nick Connolly
2021-02-15  9:56                     ` [SPDK] Re: [dpdk-dev] " Nick Connolly
2021-02-15 10:15                     ` [dpdk-dev] [SPDK] " David Marchand
2021-02-15 10:16                       ` [SPDK] Re: [dpdk-dev] " 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=f7th7ml5l6o.fsf@dhcp-25.97.bos.redhat.com \
    --to=aconole@redhat.com \
    --cc=blo@iol.unh.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.