automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: pascal.mazon@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw23645 [PATCH 4/5] net/tap: create netdevice during probing
Date: 14 Apr 2017 03:59:56 -0700	[thread overview]
Message-ID: <ffb989$26kpb1@orsmga002.jf.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Pascal Mazon <pascal.mazon@6wind.com>
Date: Fri, 14 Apr 2017 11:32:45 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
                   Repo:dpdk-next-crypto, Branch:master, CommitID:2696ec6715c2a7276f75483515b031f95af28d2e
                   Repo:dpdk-next-net, Branch:master, CommitID:7c63770abcad2150e57f3ce7f271b80a0cff9797
                   Repo:dpdk-next-virtio, Branch:master, CommitID:5cd653a4125d751fd7ea98a29afe42d9da8aab7a
                   Repo:dpdk, Branch:master, CommitID:fc0ddc684877b7aa0c4733ab5619a2487e396155
                   
Apply patch file failed:
Repo: dpdk
23645:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 succeeded at 109 (offset -4 lines).
Hunk #2 succeeded at 117 (offset -4 lines).
Hunk #3 succeeded at 216 (offset -4 lines).
Hunk #4 FAILED at 756.
Hunk #5 succeeded at 1064 (offset 5 lines).
Hunk #6 FAILED at 1136.
2 out of 6 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej

Repo: dpdk-next-crypto
23645:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 succeeded at 109 (offset -4 lines).
Hunk #2 succeeded at 117 (offset -4 lines).
Hunk #3 succeeded at 216 (offset -4 lines).
Hunk #4 FAILED at 756.
Hunk #5 succeeded at 1064 (offset 5 lines).
Hunk #6 FAILED at 1136.
2 out of 6 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej

Repo: dpdk-next-net
23645:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 succeeded at 109 (offset -4 lines).
Hunk #2 succeeded at 117 (offset -4 lines).
Hunk #3 succeeded at 216 (offset -4 lines).
Hunk #4 FAILED at 756.
Hunk #5 succeeded at 1064 (offset 5 lines).
Hunk #6 FAILED at 1136.
2 out of 6 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej

Repo: dpdk-next-virtio
23645:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 succeeded at 109 (offset -4 lines).
Hunk #2 succeeded at 117 (offset -4 lines).
Hunk #3 succeeded at 216 (offset -4 lines).
Hunk #4 FAILED at 756.
Hunk #5 succeeded at 1064 (offset 5 lines).
Hunk #6 FAILED at 1136.
2 out of 6 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej

Repo: dpdk-next-eventdev
23645:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 113.
Hunk #2 succeeded at 118 (offset -7 lines).
Hunk #3 FAILED at 224.
Hunk #4 FAILED at 829.
Hunk #5 succeeded at 647 (offset -485 lines).
Hunk #6 FAILED at 1209.
4 out of 6 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej


DPDK STV team

                 reply	other threads:[~2017-04-14 10:59 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='ffb989$26kpb1@orsmga002.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=pascal.mazon@6wind.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).