DPDK CI discussions
 help / color / mirror / Atom feed
From: Brandon Lo <blo@iol.unh.edu>
To: Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: David Marchand <david.marchand@redhat.com>,
	 "Zawadzki, Tomasz" <tomasz.zawadzki@intel.com>,
	dpdklab <dpdklab@iol.unh.edu>,
	 Thomas Monjalon <thomas@monjalon.net>,
	"ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-ci] [dpdklab] Re:  SPDK compilation issue
Date: Wed, 18 Nov 2020 10:56:42 -0500	[thread overview]
Message-ID: <CAOeXdva99Ba+utg93d2NO-AGz1ynBvSp35cdfOMTpwFr=-JoKQ@mail.gmail.com> (raw)
In-Reply-To: <CAOE1vsPf8229LfHuc28UVd-LuLMBmbnnsZrzqGbDo7zevpBP4Q@mail.gmail.com>

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

Hi everyone,

The SPDK compile job pulls from the LTS branch before every SPDK compile
test.
I have checked the local repository and it currently shows that it did pick
up the commit 'a73286870ebf189629937515bd28714937f2498b: env_dpdk/pci:
adapt to 20.11 EAL changes'

Looking at the logs, I can see the changes have taken place. However, the
error/warning messages are the same, and they highlight the lines that have
already been changed.
This issue persists after clearing the cache and rebuilding the container
used to compile. Has anyone had an issue like this before?

Thanks,
Brandon

On Wed, Nov 18, 2020 at 9:09 AM Lincoln Lavoie <lylavoie@iol.unh.edu> wrote:

> Hi David,
>
> Let me check with Brandon.  I believe it should pick it up, but I'm not
> 100% sure.  We generally don't track the downstream branches as closely
> because the goal is testing DPDK patches with a "stable" system, i.e. not
> having a patch on SDPK testing cause a failure on DPDK CI.
>
> Cheers,
> Lincoln
>
> On Wed, Nov 18, 2020 at 4:32 AM David Marchand <david.marchand@redhat.com>
> wrote:
>
>> Hello,
>>
>> On Wed, Nov 18, 2020 at 9:36 AM Zawadzki, Tomasz
>> <tomasz.zawadzki@intel.com> wrote:
>> >
>> > Hi David,
>> >
>> > The change is now integrated into SPDK. Checking out branch v20.10.x
>> will allow to resume SPDK job at UNH.
>>
>> Thanks Tomasz!
>>
>> Lincoln,
>> Do you know when this change will be picked up by the UNH 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>
>


-- 

Brandon Lo

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

blo@iol.unh.edu

www.iol.unh.edu

[-- Attachment #2: Type: text/html, Size: 4830 bytes --]

  reply	other threads:[~2020-11-18 15:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17  7:35 [dpdk-ci] " David Marchand
2020-11-17 13:22 ` Lincoln Lavoie
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 [this message]
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='CAOeXdva99Ba+utg93d2NO-AGz1ynBvSp35cdfOMTpwFr=-JoKQ@mail.gmail.com' \
    --to=blo@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dpdklab@iol.unh.edu \
    --cc=lylavoie@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).