automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| pw72454 [PATCH] [v2] build: replace meson OS detection with variable
Date: Tue, 30 Jun 2020 09:27:38 -0400 (EDT)	[thread overview]
Message-ID: <20200630132738.3FAB36D437@noxus.dpdklab.iol.unh.edu> (raw)

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

Test-Label: Performance-Testing
Test-Status: FAILURE
http://dpdk.org/patch/72454

_build patch failure_

Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Tuesday, June 30 2020 13:15:22 
Applied on: CommitID:014a7ec6c418eaf24a13be8ade8229638ddc6eed
Apply patch set 72454 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/11741/

UNH-IOL DPDK Community Lab

                 reply	other threads:[~2020-06-30 13:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200630132738.3FAB36D437@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).