automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: ferruh.yigit@intel.com
Subject: [dpdk-test-report] |FAILURE| pw18131 [PATCH v5 21/29] app/testpmd: add command to test VF broadcast mode on i40e
Date: 17 Dec 2016 09:58:42 -0800	[thread overview]
Message-ID: <9ddf0d$10pm65l@fmsmga002.fm.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2029 bytes --]

Test-Label: Intel compilation
Test-Status: FAILURE
http://dpdk.org/patch/18131

_apply patch file failure_

Submitter: Ferruh Yigit <ferruh.yigit@intel.com>
Date: Fri, 16 Dec 2016 19:02:49 +0000
DPDK git baseline: Repo:dpdk-next-crypto, Branch:master, CommitID:ee103f0ee24a8f2f2243f128796608028fc8ef4d
                   Repo:dpdk-next-net, Branch:master, CommitID:f4fa617532e5ffa71f0cedc9f37fda069c8eb856
                   Repo:dpdk-next-virtio, Branch:master, CommitID:584b07eea17fbd5977df4301baae114494855d64
                   Repo:dpdk, Branch:master, CommitID:c431384c8fbf8503693bcae1bdcd58d6fa459b8a
                   
Apply patch file failed:
Repo: dpdk-next-crypto
18131:
patching file app/test-pmd/cmdline.c
Hunk #1 succeeded at 276 with fuzz 2 (offset -3 lines).
Hunk #2 succeeded at 7607 with fuzz 1 (offset -4133 lines).
Hunk #3 FAILED at 11995.
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-net
18131:
patching file app/test-pmd/cmdline.c
Hunk #1 succeeded at 276 with fuzz 2 (offset -3 lines).
Hunk #2 succeeded at 7615 with fuzz 1 (offset -4125 lines).
Hunk #3 FAILED at 11995.
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
18131:
patching file app/test-pmd/cmdline.c
Hunk #1 succeeded at 276 with fuzz 2 (offset -3 lines).
Hunk #2 succeeded at 7588 with fuzz 1 (offset -4152 lines).
Hunk #3 FAILED at 11995.
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
18131:
patching file app/test-pmd/cmdline.c
Hunk #1 succeeded at 276 with fuzz 2 (offset -3 lines).
Hunk #2 succeeded at 7607 with fuzz 1 (offset -4133 lines).
Hunk #3 FAILED at 11995.
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-17 17:58 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='9ddf0d$10pm65l@fmsmga002.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=ferruh.yigit@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).