From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: qi.z.zhang@intel.com
Subject: [dpdk-test-report] |FAILURE| pw18025 [PATCH v3 20/29] app/testpmd: use multicast promiscuous mode on i40e
Date: 15 Dec 2016 22:01:11 -0800 [thread overview]
Message-ID: <69c10c$vuvn4i@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]
Test-Label: Intel compilation
Test-Status: FAILURE
http://dpdk.org/patch/18025
_apply patch file failure_
Submitter: Qi Zhang <qi.z.zhang@intel.com>
Date: Thu, 15 Dec 2016 16:04:52 -0500
DPDK git baseline: Repo:dpdk-next-crypto, Branch:master, CommitID:d753dc372ec556c1c4e2ff4966a10c7441df7ea6
Repo:dpdk-next-net, Branch:master, CommitID:537fb4de02b90637320427f36e447f6243c01867
Repo:dpdk-next-virtio, Branch:master, CommitID:584b07eea17fbd5977df4301baae114494855d64
Repo:dpdk, Branch:master, CommitID:c431384c8fbf8503693bcae1bdcd58d6fa459b8a
Apply patch file failed:
Repo: dpdk-next-crypto
18025:
patching file app/test-pmd/cmdline.c
Hunk #2 succeeded at 11542 (offset -110 lines).
Hunk #3 FAILED at 11899.
1 out of 3 hunks FAILED -- saving rejects to file app/test-pmd/cmdline.c.rej
patching file doc/guides/testpmd_app_ug/testpmd_funcs.rst
Repo: dpdk-next-virtio
18025:
patching file app/test-pmd/cmdline.c
Hunk #2 succeeded at 11494 (offset -158 lines).
Hunk #3 FAILED at 11899.
1 out of 3 hunks FAILED -- saving rejects to file app/test-pmd/cmdline.c.rej
patching file doc/guides/testpmd_app_ug/testpmd_funcs.rst
Repo: dpdk
18025:
patching file app/test-pmd/cmdline.c
Hunk #2 succeeded at 11542 (offset -110 lines).
Hunk #3 FAILED at 11899.
1 out of 3 hunks FAILED -- saving rejects to file app/test-pmd/cmdline.c.rej
patching file doc/guides/testpmd_app_ug/testpmd_funcs.rst
DPDK STV team
reply other threads:[~2016-12-16 6:01 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='69c10c$vuvn4i@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=qi.z.zhang@intel.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).