From: sys_stv@intel.com
To: yongjiex.gu@intel.com, weichunx.chen@intel.com,
huilongx.xu@intel.com, gangx.xu@intel.com, peipeix.lu@intel.com,
olivier.matz@6wind.com, test-report@dpdk.org
Subject: [dpdk-test-report] [Patchwork]|ERROR| pw17226-17231 virtio/mbuf: fix virtio tso with shared mbufs
Date: 24 Nov 2016 01:21:59 -0800 [thread overview]
Message-ID: <587443$8dbrh@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2404 bytes --]
Test-Label: Intel Compilation on Fedora
Test-Status: ERROR
Patchwork ID: 17226-17231
http://www.dpdk.org/dev/patchwork/patch/17231/
Submitter: Olivier Matz <olivier.matz@6wind.com>
Date: Thu, 24 Nov 2016 09:56:33 +0100
DPDK git baseline: 3549dd67152d26e46b136286ee0296a9aaa1923d
patch file error:
17226:
patching file app/test/test_mbuf.c
patching file lib/librte_mbuf/rte_mbuf.c
Hunk #1 succeeded at 262 with fuzz 1 (offset -36 lines).
patching file lib/librte_mbuf/rte_mbuf.h
Hunk #1 succeeded at 1958 (offset 280 lines).
patching file lib/librte_mbuf/rte_mbuf_version.map
Hunk #1 FAILED at 35.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_mbuf/rte_mbuf_version.map.rej
17227:
patching file app/test/test_mbuf.c
Hunk #1 succeeded at 429 with fuzz 1 (offset -22 lines).
patching file lib/librte_mbuf/rte_mbuf.h
Hunk #1 FAILED at 1643.
Hunk #2 succeeded at 2008 (offset 280 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_mbuf/rte_mbuf.h.rej
17228:
patching file lib/librte_mbuf/rte_mbuf.c
Hunk #1 FAILED at 279.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_mbuf/rte_mbuf.c.rej
patching file lib/librte_mbuf/rte_mbuf.h
Hunk #1 FAILED at 1671.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_mbuf/rte_mbuf.h.rej
patching file drivers/net/virtio/virtio_rxtx.c
Hunk #1 FAILED at 225.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/virtio/virtio_rxtx.c.rej
17229:
patching file lib/librte_mbuf/rte_mbuf.c
Hunk #1 FAILED at 265.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_mbuf/rte_mbuf.c.rej
patching file lib/librte_mbuf/rte_mbuf.h
Hunk #1 FAILED at 1576.
Hunk #2 FAILED at 1599.
2 out of 2 hunks FAILED -- saving rejects to file lib/librte_mbuf/rte_mbuf.h.rej
17230:
patching file drivers/net/virtio/virtio_rxtx.c
Hunk #1 FAILED at 211.
Hunk #2 FAILED at 268.
Hunk #3 succeeded at 250 (offset -53 lines).
Hunk #4 FAILED at 315.
Hunk #5 FAILED at 347.
Hunk #6 FAILED at 364.
5 out of 6 hunks FAILED -- saving rejects to file drivers/net/virtio/virtio_rxtx.c.rej
patching file drivers/net/virtio/virtqueue.h
Hunk #1 succeeded at 238 (offset -16 lines).
17231:
patching file app/test/test_mbuf.c
patching file lib/librte_mbuf/rte_mbuf.h
Hunk #1 succeeded at 965 (offset 389 lines).
Hunk #2 FAILED at 1574.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_mbuf/rte_mbuf.h.rej
DPDK STV team
reply other threads:[~2016-11-24 9:22 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='587443$8dbrh@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=gangx.xu@intel.com \
--cc=huilongx.xu@intel.com \
--cc=olivier.matz@6wind.com \
--cc=peipeix.lu@intel.com \
--cc=test-report@dpdk.org \
--cc=weichunx.chen@intel.com \
--cc=yongjiex.gu@intel.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).