From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw51835[v4] service: fix parameter type
Date: 28 Mar 2019 00:05:08 -0700 [thread overview]
Message-ID: <e75792$6g5ls1@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3036 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/51835
_apply issues_
Submitter: Nikhil Rao <nikhil.rao@intel.com>
Date: 2019-03-28 06:29:03
Reply_mail: 1553754543-40534-1-git-send-email-nikhil.rao@intel.com
DPDK git baseline:
Repo:dpdk-master, CommitID: 85cffb2eccd9edf89a9e28539206a79258a6e9d9
Repo:dpdk-next-eventdev, CommitID: 744407cf7b80f9e5c886c2304211b429febb4394
Repo:dpdk-next-net, CommitID: 64e5f66546329e8495986d841c11aa7ce45edcbf
Repo:dpdk-next-crypto, CommitID: 0bcc66441d1ed8c2759ac05cfcfc3144de288b85
Repo:dpdk-next-virtio, CommitID: daf8de5c41dfbe40f354ff009f5791db348e0b09
*Repo: dpdk-master
Checking patch lib/librte_eal/common/include/rte_service.h...
Checking patch app/test/test_service_cores.c...
Checking patch lib/librte_eal/common/rte_service.c...
Checking patch lib/librte_eal/bsdapp/eal/Makefile...
error: lib/librte_eal/bsdapp/eal/Makefile: No such file or directory
Checking patch lib/librte_eal/linuxapp/eal/Makefile...
error: lib/librte_eal/linuxapp/eal/Makefile: No such file or directory
Checking patch lib/librte_eal/meson.build...
*Repo: dpdk-next-eventdev
Checking patch lib/librte_eal/common/include/rte_service.h...
Checking patch app/test/test_service_cores.c...
Checking patch lib/librte_eal/common/rte_service.c...
Checking patch lib/librte_eal/bsdapp/eal/Makefile...
error: lib/librte_eal/bsdapp/eal/Makefile: No such file or directory
Checking patch lib/librte_eal/linuxapp/eal/Makefile...
error: lib/librte_eal/linuxapp/eal/Makefile: No such file or directory
Checking patch lib/librte_eal/meson.build...
*Repo: dpdk-next-net
Checking patch lib/librte_eal/common/include/rte_service.h...
Checking patch app/test/test_service_cores.c...
Checking patch lib/librte_eal/common/rte_service.c...
Checking patch lib/librte_eal/bsdapp/eal/Makefile...
error: lib/librte_eal/bsdapp/eal/Makefile: No such file or directory
Checking patch lib/librte_eal/linuxapp/eal/Makefile...
error: lib/librte_eal/linuxapp/eal/Makefile: No such file or directory
Checking patch lib/librte_eal/meson.build...
*Repo: dpdk-next-crypto
Checking patch lib/librte_eal/common/include/rte_service.h...
Checking patch app/test/test_service_cores.c...
Checking patch lib/librte_eal/common/rte_service.c...
Checking patch lib/librte_eal/bsdapp/eal/Makefile...
error: lib/librte_eal/bsdapp/eal/Makefile: No such file or directory
Checking patch lib/librte_eal/linuxapp/eal/Makefile...
error: lib/librte_eal/linuxapp/eal/Makefile: No such file or directory
Checking patch lib/librte_eal/meson.build...
*Repo: dpdk-next-virtio
Checking patch lib/librte_eal/common/include/rte_service.h...
Checking patch app/test/test_service_cores.c...
Checking patch lib/librte_eal/common/rte_service.c...
Checking patch lib/librte_eal/bsdapp/eal/Makefile...
error: lib/librte_eal/bsdapp/eal/Makefile: No such file or directory
Checking patch lib/librte_eal/linuxapp/eal/Makefile...
error: lib/librte_eal/linuxapp/eal/Makefile: No such file or directory
Checking patch lib/librte_eal/meson.build...
DPDK STV team
reply other threads:[~2019-03-28 7:05 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$6g5ls1@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).