automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: ophirmu@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw38667 [PATCH v2 2/2] net/tap: support TSO (TCP Segment Offload)
Date: 04 May 2018 04:31:21 -0700	[thread overview]
Message-ID: <0590c7$1ima8k@orsmga001.jf.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Ophir Munk <ophirmu@mellanox.com>
Date: Sun, 22 Apr 2018 11:30:11 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fcde84b5f85b3c1a5d5564299fd49c58ca20370d
                   Repo:dpdk-next-crypto, Branch:master, CommitID:7baac775945ce26f4740158656965f095dc4dbda
                   Repo:dpdk-next-net, Branch:master, CommitID:ee73f98ef481f61eab2f7289f033c6f9113eee8a
                   Repo:dpdk-next-virtio, Branch:master, CommitID:81daf0ba4f2eb20c00975b474cb9b6ab71c44e25
                   Repo:dpdk, Branch:master, CommitID:ee73f98ef481f61eab2f7289f033c6f9113eee8a
                   
Apply patch file failed:
Repo: dpdk
38667:
patching file drivers/net/tap/Makefile
patching file drivers/net/tap/rte_eth_tap.c
Hunk #2 succeeded at 406 with fuzz 1 (offset -3 lines).
Hunk #3 FAILED at 419.
Hunk #4 succeeded at 490 (offset -12 lines).
Hunk #5 succeeded at 506 (offset -12 lines).
Hunk #6 succeeded at 545 (offset -12 lines).
Hunk #7 succeeded at 586 (offset -12 lines).
Hunk #8 FAILED at 1118.
Hunk #9 succeeded at 1159 (offset -11 lines).
2 out of 9 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
patching file drivers/net/tap/rte_eth_tap.h
Hunk #1 FAILED at 15.
Hunk #2 succeeded at 23 (offset 1 line).
Hunk #3 succeeded at 53 (offset 1 line).
1 out of 3 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.h.rej
patching file mk/rte.app.mk

Repo: dpdk-next-crypto
38667:
patching file drivers/net/tap/Makefile
patching file drivers/net/tap/rte_eth_tap.c
Hunk #2 succeeded at 406 with fuzz 1 (offset -3 lines).
Hunk #3 FAILED at 419.
Hunk #4 succeeded at 490 (offset -12 lines).
Hunk #5 succeeded at 506 (offset -12 lines).
Hunk #6 succeeded at 545 (offset -12 lines).
Hunk #7 succeeded at 586 (offset -12 lines).
Hunk #8 FAILED at 1118.
Hunk #9 succeeded at 1159 (offset -11 lines).
2 out of 9 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
patching file drivers/net/tap/rte_eth_tap.h
Hunk #1 FAILED at 15.
Hunk #2 succeeded at 23 (offset 1 line).
Hunk #3 succeeded at 53 (offset 1 line).
1 out of 3 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.h.rej
patching file mk/rte.app.mk

Repo: dpdk-next-net
38667:
patching file drivers/net/tap/Makefile
patching file drivers/net/tap/rte_eth_tap.c
Hunk #2 succeeded at 406 with fuzz 1 (offset -3 lines).
Hunk #3 FAILED at 419.
Hunk #4 succeeded at 490 (offset -12 lines).
Hunk #5 succeeded at 506 (offset -12 lines).
Hunk #6 succeeded at 545 (offset -12 lines).
Hunk #7 succeeded at 586 (offset -12 lines).
Hunk #8 FAILED at 1118.
Hunk #9 succeeded at 1159 (offset -11 lines).
2 out of 9 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
patching file drivers/net/tap/rte_eth_tap.h
Hunk #1 FAILED at 15.
Hunk #2 succeeded at 23 (offset 1 line).
Hunk #3 succeeded at 53 (offset 1 line).
1 out of 3 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.h.rej
patching file mk/rte.app.mk

Repo: dpdk-next-virtio
38667:
patching file drivers/net/tap/Makefile
patching file drivers/net/tap/rte_eth_tap.c
Hunk #6 FAILED at 558.
Hunk #7 succeeded at 568 with fuzz 1 (offset -32 lines).
Hunk #8 succeeded at 1088 (offset -32 lines).
Hunk #9 succeeded at 1185 (offset -32 lines).
1 out of 9 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
patching file drivers/net/tap/rte_eth_tap.h
patching file mk/rte.app.mk

Repo: dpdk-next-eventdev
38667:
patching file drivers/net/tap/Makefile
patching file drivers/net/tap/rte_eth_tap.c
Hunk #2 succeeded at 406 with fuzz 1 (offset -3 lines).
Hunk #3 FAILED at 419.
Hunk #4 succeeded at 490 (offset -12 lines).
Hunk #5 succeeded at 506 (offset -12 lines).
Hunk #6 succeeded at 545 (offset -12 lines).
Hunk #7 succeeded at 586 (offset -12 lines).
Hunk #8 FAILED at 1118.
Hunk #9 succeeded at 1159 (offset -11 lines).
2 out of 9 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
patching file drivers/net/tap/rte_eth_tap.h
Hunk #1 FAILED at 15.
Hunk #2 succeeded at 23 (offset 1 line).
Hunk #3 succeeded at 53 (offset 1 line).
1 out of 3 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.h.rej
patching file mk/rte.app.mk


DPDK STV team

                 reply	other threads:[~2018-05-04 11:31 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$1ima8k@orsmga001.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=ophirmu@mellanox.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).