From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: yskoh@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw38764 [PATCH v4 1/2] mbuf: support attaching external buffer to mbuf
Date: 06 May 2018 19:13:18 -0700 [thread overview]
Message-ID: <0590c7$1j6rtk@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3140 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38764
_apply patch file failure_
Submitter: Yongseok Koh <yskoh@mellanox.com>
Date: Mon, 23 Apr 2018 18:38:53 -0700
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fcde84b5f85b3c1a5d5564299fd49c58ca20370d
Repo:dpdk-next-crypto, Branch:master, CommitID:7baac775945ce26f4740158656965f095dc4dbda
Repo:dpdk-next-net, Branch:master, CommitID:29f4ab844cdb61d7241f7241fe860779516b9012
Repo:dpdk-next-virtio, Branch:master, CommitID:037c0996bc927342f157426739e0cb63f2db8689
Repo:dpdk, Branch:master, CommitID:ee73f98ef481f61eab2f7289f033c6f9113eee8a
Apply patch file failed:
Repo: dpdk
38764:
patching file lib/librte_mbuf/rte_mbuf.h
Hunk #1 FAILED at 326.
Hunk #2 FAILED at 566.
Hunk #3 FAILED at 688.
Hunk #4 succeeded at 934 with fuzz 2 (offset 113 lines).
Hunk #5 FAILED at 1247.
Hunk #6 FAILED at 1265.
Hunk #7 FAILED at 1293.
Hunk #8 FAILED at 1302.
Hunk #9 FAILED at 1316.
Hunk #10 FAILED at 1331.
Hunk #11 FAILED at 1361.
Hunk #12 FAILED at 1373.
11 out of 12 hunks FAILED -- saving rejects to file lib/librte_mbuf/rte_mbuf.h.rej
Repo: dpdk-next-crypto
38764:
patching file lib/librte_mbuf/rte_mbuf.h
Hunk #1 FAILED at 326.
Hunk #2 FAILED at 566.
Hunk #3 FAILED at 688.
Hunk #4 succeeded at 934 with fuzz 2 (offset 113 lines).
Hunk #5 FAILED at 1247.
Hunk #6 FAILED at 1265.
Hunk #7 FAILED at 1293.
Hunk #8 FAILED at 1302.
Hunk #9 FAILED at 1316.
Hunk #10 FAILED at 1331.
Hunk #11 FAILED at 1361.
Hunk #12 FAILED at 1373.
11 out of 12 hunks FAILED -- saving rejects to file lib/librte_mbuf/rte_mbuf.h.rej
Repo: dpdk-next-net
38764:
patching file lib/librte_mbuf/rte_mbuf.h
Hunk #1 FAILED at 326.
Hunk #2 FAILED at 566.
Hunk #3 FAILED at 688.
Hunk #4 succeeded at 934 with fuzz 2 (offset 113 lines).
Hunk #5 FAILED at 1247.
Hunk #6 FAILED at 1265.
Hunk #7 FAILED at 1293.
Hunk #8 FAILED at 1302.
Hunk #9 FAILED at 1316.
Hunk #10 FAILED at 1331.
Hunk #11 FAILED at 1361.
Hunk #12 FAILED at 1373.
11 out of 12 hunks FAILED -- saving rejects to file lib/librte_mbuf/rte_mbuf.h.rej
Repo: dpdk-next-virtio
38764:
patching file lib/librte_mbuf/rte_mbuf.h
Hunk #1 FAILED at 326.
Hunk #2 FAILED at 566.
Hunk #3 FAILED at 688.
Hunk #4 succeeded at 934 with fuzz 2 (offset 113 lines).
Hunk #5 FAILED at 1247.
Hunk #6 FAILED at 1265.
Hunk #7 FAILED at 1293.
Hunk #8 FAILED at 1302.
Hunk #9 FAILED at 1316.
Hunk #10 FAILED at 1331.
Hunk #11 FAILED at 1361.
Hunk #12 FAILED at 1373.
11 out of 12 hunks FAILED -- saving rejects to file lib/librte_mbuf/rte_mbuf.h.rej
Repo: dpdk-next-eventdev
38764:
patching file lib/librte_mbuf/rte_mbuf.h
Hunk #1 FAILED at 326.
Hunk #2 FAILED at 566.
Hunk #3 FAILED at 688.
Hunk #4 succeeded at 934 with fuzz 2 (offset 113 lines).
Hunk #5 FAILED at 1247.
Hunk #6 FAILED at 1265.
Hunk #7 FAILED at 1293.
Hunk #8 FAILED at 1302.
Hunk #9 FAILED at 1316.
Hunk #10 FAILED at 1331.
Hunk #11 FAILED at 1361.
Hunk #12 FAILED at 1373.
11 out of 12 hunks FAILED -- saving rejects to file lib/librte_mbuf/rte_mbuf.h.rej
DPDK STV team
reply other threads:[~2018-05-07 2:13 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='0590c7$1j6rtk@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=yskoh@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).