From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xuemingl@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw37965 [PATCH v3 2/5] ethdev: introduce new tunnel VXLAN-GPE
Date: 25 Apr 2018 01:34:27 -0700 [thread overview]
Message-ID: <ca5293$1feqir@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1683 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/37965
_apply patch file failure_
Submitter: Xueming Li <xuemingl@mellanox.com>
Date: Thu, 12 Apr 2018 15:33:20 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fe5abd3150bc1caa8369e743c395c39f53265597
Repo:dpdk-next-crypto, Branch:master, CommitID:eb8a86e275ef15a5455948d679d1a2c43dd4c740
Repo:dpdk-next-net, Branch:master, CommitID:329502143e095229f8e90d5064849443c4250ef9
Repo:dpdk-next-virtio, Branch:master, CommitID:81daf0ba4f2eb20c00975b474cb9b6ab71c44e25
Repo:dpdk, Branch:master, CommitID:2ed9bf330709e75c2f066f6ec13ece1ecdb4e9db
Apply patch file failed:
Repo: dpdk-next-net
37965:
patching file doc/guides/prog_guide/rte_flow.rst
Hunk #1 succeeded at 992 (offset -52 lines).
patching file lib/librte_ether/rte_eth_ctrl.h
patching file lib/librte_ether/rte_flow.c
Hunk #1 succeeded at 54 (offset -1 lines).
patching file lib/librte_ether/rte_flow.h
Hunk #1 succeeded at 325 (offset -10 lines).
Hunk #2 succeeded at 824 (offset -47 lines).
patching file lib/librte_mbuf/rte_mbuf.c
Hunk #1 FAILED at 405.
Hunk #2 succeeded at 430 with fuzz 2 (offset -9 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_mbuf/rte_mbuf.c.rej
patching file lib/librte_mbuf/rte_mbuf.h
Hunk #1 FAILED at 210.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_mbuf/rte_mbuf.h.rej
patching file lib/librte_mbuf/rte_mbuf_ptype.c
patching file lib/librte_mbuf/rte_mbuf_ptype.h
patching file lib/librte_net/rte_ether.h
Hunk #1 succeeded at 310 (offset -1 lines).
DPDK STV team
reply other threads:[~2018-04-25 8:34 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='ca5293$1feqir@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@mellanox.com \
/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).