From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: Brandon Lo <blo@iol.unh.edu>
Cc: "Tu, Lijuan" <lijuan.tu@intel.com>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
"ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-ci] Building TestPMD in DPDK
Date: Tue, 20 Oct 2020 11:35:48 -0400 [thread overview]
Message-ID: <CAOE1vsMjKZGSpK+s_haUsOXh7ZsJDfge97A3suWMGtev4NXK2Q@mail.gmail.com> (raw)
In-Reply-To: <CAOeXdvZkV2p9tFD85UVpX=_F=iD0yf1oDHy9ecRNbBsV-xRTdw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3482 bytes --]
This is the patch I was talking about, where we might now be missing a
requirement on those systems:
https://mails.dpdk.org/archives/ci/2020-October/000815.html
Cheers,
Lincoln
On Tue, Oct 20, 2020 at 9:56 AM Brandon Lo <blo@iol.unh.edu> wrote:
> Hi Lijuan,
>
> Yes, we have "build_type=meson" in the execution.cfg file.
>
> DTS compiles DPDK using these commands:
> "CC=gcc meson --werror -Denable_kmods=True -Dlibdir=lib
> --default-library=static x86_64-native-linuxapp-gcc"
> and
> "ninja -C x86_64-native-linuxapp-gcc -j 62"
>
> Running functional tests, we get:
> "x86_64-native-linuxapp-gcc/app/dpdk-testpmd: No such file or directory"
>
> Thanks,
> Brandon
>
> On Tue, Oct 20, 2020 at 9:53 AM Tu, Lijuan <lijuan.tu@intel.com> wrote:
>
>> I mean config “build_type=meson” in DTS/execution.cfg, Snice DPDK don’t
>> support “make” now, we have to use meson build.
>>
>>
>>
>> *From:* ci <ci-bounces@dpdk.org> *On Behalf Of *Tu, Lijuan
>> *Sent:* 2020年10月20日 21:40
>> *To:* Brandon Lo <blo@iol.unh.edu>; Lincoln Lavoie <lylavoie@iol.unh.edu>;
>> Chen, Zhaoyan <zhaoyan.chen@intel.com>
>> *Cc:* Thomas Monjalon <thomas@monjalon.net>; ci@dpdk.org
>> *Subject:* Re: [dpdk-ci] Building TestPMD in DPDK
>>
>>
>>
>> Did you use meson build ?
>>
>>
>>
>> *From:* Brandon Lo <blo@iol.unh.edu>
>> *Sent:* 2020年10月20日 21:19
>> *To:* Lincoln Lavoie <lylavoie@iol.unh.edu>; Tu, Lijuan <
>> lijuan.tu@intel.com>; Chen, Zhaoyan <zhaoyan.chen@intel.com>
>> *Cc:* Thomas Monjalon <thomas@monjalon.net>; ci@dpdk.org
>> *Subject:* Re: [dpdk-ci] Building TestPMD in DPDK
>>
>>
>>
>> I think this should be brought up to the DTS maintainers.
>> DTS' initial behavior is to build DPDK/testpmd, and it assumes that
>> testpmd is in the build's output directory.
>>
>>
>>
>> Thanks,
>>
>> Brandon
>>
>>
>>
>> On Tue, Oct 20, 2020 at 8:38 AM Lincoln Lavoie <lylavoie@iol.unh.edu>
>> wrote:
>>
>> 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>
>>
>>
>>
>>
>> --
>>
>> Brandon Lo
>>
>> UNH InterOperability Laboratory
>>
>> 21 Madbury Rd, Suite 100, Durham, NH 03824
>>
>> blo@iol.unh.edu
>>
>> 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
>
--
*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: 11855 bytes --]
next prev parent reply other threads:[~2020-10-20 15:37 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
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 [this message]
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=CAOE1vsMjKZGSpK+s_haUsOXh7ZsJDfge97A3suWMGtev4NXK2Q@mail.gmail.com \
--to=lylavoie@iol.unh.edu \
--cc=blo@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=lijuan.tu@intel.com \
--cc=thomas@monjalon.net \
--cc=zhaoyan.chen@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).