From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: allain.legacy@windriver.com
Subject: [dpdk-test-report] |FAILURE| pw22163 [PATCH v5 03/14] net/avp: debug log macros
Date: 23 Mar 2017 11:25:27 -0700 [thread overview]
Message-ID: <ffb989$1t7uda@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1770 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/22163
_apply patch file failure_
Submitter: Allain Legacy <allain.legacy@windriver.com>
Date: Thu, 23 Mar 2017 07:24:02 -0400
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:1df5f2222142242be872e47628a22e0bd0887a81
Repo:dpdk-next-crypto, Branch:master, CommitID:1b16ada4eeeb8c021c6b91692d0b80ecb3d9702e
Repo:dpdk-next-net, Branch:master, CommitID:b36be54c55e82610c801d1db842ee229e389a7ce
Repo:dpdk-next-virtio, Branch:master, CommitID:922c87ff9fc456921ee5b673ac747da420f63bae
Repo:dpdk, Branch:master, CommitID:84aac97b49994be6b461b46be160b47938e697b3
Apply patch file failed:
Repo: dpdk
22163:
patching file config/common_base
Hunk #1 FAILED at 356.
1 out of 1 hunk FAILED -- saving rejects to file config/common_base.rej
patching file drivers/net/avp/avp_logs.h
Repo: dpdk-next-crypto
22163:
patching file config/common_base
Hunk #1 FAILED at 356.
1 out of 1 hunk FAILED -- saving rejects to file config/common_base.rej
patching file drivers/net/avp/avp_logs.h
Repo: dpdk-next-net
22163:
patching file config/common_base
Hunk #1 FAILED at 356.
1 out of 1 hunk FAILED -- saving rejects to file config/common_base.rej
patching file drivers/net/avp/avp_logs.h
Repo: dpdk-next-virtio
22163:
patching file config/common_base
Hunk #1 FAILED at 356.
1 out of 1 hunk FAILED -- saving rejects to file config/common_base.rej
patching file drivers/net/avp/avp_logs.h
Repo: dpdk-next-eventdev
22163:
patching file config/common_base
Hunk #1 FAILED at 356.
1 out of 1 hunk FAILED -- saving rejects to file config/common_base.rej
patching file drivers/net/avp/avp_logs.h
DPDK STV team
reply other threads:[~2017-03-23 18:25 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='ffb989$1t7uda@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=allain.legacy@windriver.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).