DPDK CI discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Brandon Lo <blo@iol.unh.edu>, ci@dpdk.org
Subject: Re: [dpdk-ci] Building TestPMD in DPDK
Date: Tue, 20 Oct 2020 08:36:44 -0400	[thread overview]
Message-ID: <CAOE1vsMGHoHUNh8ucevr-Q-rVSeb229EF40bGatVDh-aG9StAA@mail.gmail.com> (raw)
In-Reply-To: <320640640.vBkTyhWo6Z@thomas>

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

Is this because of the change that adds some python requirements to
testpmd? I remember seeing something about that go by on the lists.

Cheers,
Lincoln

On Tue, Oct 20, 2020 at 8:34 AM Thomas Monjalon <thomas@monjalon.net> wrote:

> 20/10/2020 14:31, Brandon Lo:
> > Hi everyone,
> >
> > Is there a new method to build the testpmd application in DPDK?
> >
> > Using the latest patches, any job in the CI that uses DTS to compile
> > DPDK and run functional/performance tests are failing because it is
> > not building testpmd.
> > We are also using the latest commit available for DTS.
>
> No testpmd should be built.
>
>
>

-- 
*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: 2014 bytes --]

  reply	other threads:[~2020-10-20 12:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-20 12:31 Brandon Lo
2020-10-20 12:34 ` Thomas Monjalon
2020-10-20 12:36   ` Lincoln Lavoie [this message]
2020-10-20 13:18     ` Brandon Lo
2020-10-20 13:39       ` Tu, Lijuan
2020-10-20 13:53         ` Tu, Lijuan
2020-10-20 13:55           ` Brandon Lo
2020-10-20 15:35             ` Lincoln Lavoie
2020-10-20 15:45               ` Brandon Lo
2020-10-21  0:50             ` Ma, LihongX

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=CAOE1vsMGHoHUNh8ucevr-Q-rVSeb229EF40bGatVDh-aG9StAA@mail.gmail.com \
    --to=lylavoie@iol.unh.edu \
    --cc=blo@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).