From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| pw73840-73854 [PATCH] [v2, 01/20] regex/mlx5: add RegEx PMD layer and mlx5 driver
Date: Sun, 12 Jul 2020 17:28:10 -0400 (EDT) [thread overview]
Message-ID: <20200712212810.84F286D437@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
Test-Label: Performance-Testing
Test-Status: FAILURE
http://dpdk.org/patch/73840
_build patch failure_
Submitter: Ori Kam <orika@mellanox.com>
Date: Sunday, July 12 2020 20:58:42
Applied on: CommitID:87520e59fb84c3ba5dbeee10d57a534fa3a70ad2
Apply patch set 73840-73854 failed:
=========================== WARNING ============================
It is recommended to build DPDK using 'meson' and 'ninja'
See https://doc.dpdk.org/guides/linux_gsg/build_dpdk.html
Building DPDK with 'make' will be deprecated in a future release
================================================================
This deprecation warning can be passed by adding MAKE_PAUSE=n
to 'make' command line or as an exported environment variable.
Press enter to continue...
/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/mk/rte.sdkroot.mk:65: recipe for target 'warning' failed
make[2]: *** [warning] Error 1
/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/mk/rte.sdkinstall.mk:60: recipe for target 'pre_install' failed
make[1]: *** [pre_install] Error 2
/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/mk/rte.sdkroot.mk:92: recipe for target 'install' failed
make: *** [install] Error 2
https://lab.dpdk.org/results/dashboard/patchsets/12020/
UNH-IOL DPDK Community Lab
next reply other threads:[~2020-07-12 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-12 21:28 dpdklab [this message]
2020-07-14 0:51 dpdklab
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=20200712212810.84F286D437@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
/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).