From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw53053[18.11] eal: fix cleanup in no-shconf mode
Date: 24 Apr 2019 08:39:56 -0700 [thread overview]
Message-ID: <e75792$6nq4h3@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/53053
_apply issues_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: 2019-04-24 15:26:10
Reply_mail: 9119aac2903c82257a136b2cea3185a00232a203.1556119511.git.anatoly.burakov@intel.com
DPDK git baseline:
Repo:dpdk-master, CommitID: 7f251bcf22c5729792f9243480af1b3c072876a5
Repo:dpdk-next-eventdev, CommitID: 7a1ccc24874e251957513aba0520500f873e276a
Repo:dpdk-next-net, CommitID: 2328de221aa3720e91aeb4804e58c5eb2fa2c735
Repo:dpdk-next-crypto, CommitID: cafeb2dc3ffbb1f8bd86f83ac9add1549c216950
Repo:dpdk-next-virtio, CommitID: 4a3c54c92a2ca4bbbc46eaa331e71c2ec4d00cc9
*Repo: dpdk-master
Checking patch lib/librte_eal/linuxapp/eal/eal.c...
error: lib/librte_eal/linuxapp/eal/eal.c: No such file or directory
*Repo: dpdk-next-eventdev
Checking patch lib/librte_eal/linuxapp/eal/eal.c...
error: lib/librte_eal/linuxapp/eal/eal.c: No such file or directory
*Repo: dpdk-next-net
Checking patch lib/librte_eal/linuxapp/eal/eal.c...
error: lib/librte_eal/linuxapp/eal/eal.c: No such file or directory
*Repo: dpdk-next-crypto
Checking patch lib/librte_eal/linuxapp/eal/eal.c...
error: lib/librte_eal/linuxapp/eal/eal.c: No such file or directory
*Repo: dpdk-next-virtio
Checking patch lib/librte_eal/linuxapp/eal/eal.c...
error: lib/librte_eal/linuxapp/eal/eal.c: No such file or directory
DPDK STV team
reply other threads:[~2019-04-24 15:39 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='e75792$6nq4h3@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--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).