From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: yanglong.wu@intel.com
Subject: [dpdk-test-report] |FAILURE| pw36633 [PATCH v2 2/2] net/i40e: convert to new Tx offloads API
Date: 28 Mar 2018 23:07:57 -0700 [thread overview]
Message-ID: <0590c7$194buq@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3587 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/36633
_apply patch file failure_
Submitter: yanglong wu <yanglong.wu@intel.com>
Date: Thu, 29 Mar 2018 13:23:16 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:34184d9779e0aa56ab841bb2502b8945e91d8cac
Repo:dpdk-next-crypto, Branch:master, CommitID:1f0b611ae4258ddb319abb283759a327f72c65e7
Repo:dpdk-next-net, Branch:master, CommitID:6c1238459bc5bc8ef367acb53de853e65125e11e
Repo:dpdk-next-virtio, Branch:master, CommitID:8d528a6d970e0ec4c752dbe21382d24cf118b86b
Repo:dpdk, Branch:master, CommitID:20526313ba41174d3e7831ee800f6e938a1d5b85
Apply patch file failed:
Repo: dpdk
36633:
patching file drivers/net/i40e/i40e_ethdev.c
Hunk #1 FAILED at 3231.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev.c.rej
patching file drivers/net/i40e/i40e_ethdev_vf.c
Hunk #1 FAILED at 2185.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev_vf.c.rej
patching file drivers/net/i40e/i40e_rxtx.c
Hunk #1 succeeded at 1972 (offset -26 lines).
Hunk #2 succeeded at 2003 (offset -26 lines).
patching file drivers/net/i40e/i40e_rxtx.h
Hunk #1 succeeded at 148 (offset -1 lines).
Repo: dpdk-next-crypto
36633:
patching file drivers/net/i40e/i40e_ethdev.c
Hunk #1 FAILED at 3231.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev.c.rej
patching file drivers/net/i40e/i40e_ethdev_vf.c
Hunk #1 FAILED at 2185.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev_vf.c.rej
patching file drivers/net/i40e/i40e_rxtx.c
Hunk #1 succeeded at 1972 (offset -26 lines).
Hunk #2 succeeded at 2003 (offset -26 lines).
patching file drivers/net/i40e/i40e_rxtx.h
Hunk #1 succeeded at 148 (offset -1 lines).
Repo: dpdk-next-net
36633:
patching file drivers/net/i40e/i40e_ethdev.c
Hunk #1 FAILED at 3231.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev.c.rej
patching file drivers/net/i40e/i40e_ethdev_vf.c
Hunk #1 FAILED at 2185.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev_vf.c.rej
patching file drivers/net/i40e/i40e_rxtx.c
Hunk #1 succeeded at 1972 (offset -26 lines).
Hunk #2 succeeded at 2003 (offset -26 lines).
patching file drivers/net/i40e/i40e_rxtx.h
Hunk #1 succeeded at 148 (offset -1 lines).
Repo: dpdk-next-virtio
36633:
patching file drivers/net/i40e/i40e_ethdev.c
Hunk #1 FAILED at 3231.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev.c.rej
patching file drivers/net/i40e/i40e_ethdev_vf.c
Hunk #1 FAILED at 2185.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev_vf.c.rej
patching file drivers/net/i40e/i40e_rxtx.c
Hunk #1 succeeded at 1972 (offset -26 lines).
Hunk #2 succeeded at 2003 (offset -26 lines).
patching file drivers/net/i40e/i40e_rxtx.h
Hunk #1 succeeded at 148 (offset -1 lines).
Repo: dpdk-next-eventdev
36633:
patching file drivers/net/i40e/i40e_ethdev.c
Hunk #1 FAILED at 3231.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev.c.rej
patching file drivers/net/i40e/i40e_ethdev_vf.c
Hunk #1 FAILED at 2185.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev_vf.c.rej
patching file drivers/net/i40e/i40e_rxtx.c
Hunk #1 succeeded at 1972 (offset -26 lines).
Hunk #2 succeeded at 2003 (offset -26 lines).
patching file drivers/net/i40e/i40e_rxtx.h
Hunk #1 succeeded at 148 (offset -1 lines).
DPDK STV team
reply other threads:[~2018-03-29 6:07 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$194buq@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=yanglong.wu@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).