automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: arybchenko@solarflare.com
Subject: [dpdk-test-report] |FAILURE| pw37433 [PATCH 7/7] net/sfc: convert to the advanced EFX RSS interface
Date: 18 Apr 2018 08:31:00 -0700	[thread overview]
Message-ID: <f7a79a$1hbt8n@orsmga002.jf.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Andrew Rybchenko <arybchenko@solarflare.com>
Date: Fri, 6 Apr 2018 18:21:19 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fe5abd3150bc1caa8369e743c395c39f53265597
                   Repo:dpdk-next-crypto, Branch:master, CommitID:b1af489e6482a2247ef36418cee803e32bc84b2e
                   Repo:dpdk-next-net, Branch:master, CommitID:c0238e6774acd5bbd8ad4567dcf17f06e71b4c60
                   Repo:dpdk-next-virtio, Branch:master, CommitID:8adbe7e4847060d091c46abcbecd3dfea8362b7a
                   Repo:dpdk, Branch:master, CommitID:fb338b80e5fa91a0bf726cfa0627a177e01e9483
                   
Apply patch file failed:
Repo: dpdk
37433:
patching file drivers/net/sfc/sfc.c
Hunk #1 succeeded at 638 (offset 60 lines).
Hunk #2 succeeded at 663 (offset 60 lines).
Hunk #3 succeeded at 688 (offset 60 lines).
Hunk #4 succeeded at 751 (offset 60 lines).
Hunk #5 succeeded at 770 (offset 60 lines).
Hunk #6 succeeded at 804 (offset 60 lines).
patching file drivers/net/sfc/sfc.h
patching file drivers/net/sfc/sfc_ethdev.c
Hunk #1 succeeded at 153 (offset -1 lines).
Hunk #2 succeeded at 1384 (offset 10 lines).
Hunk #3 succeeded at 1424 (offset 10 lines).
Hunk #4 succeeded at 1461 (offset 10 lines).
patching file drivers/net/sfc/sfc_flow.c
Hunk #1 FAILED at 1268.
Hunk #2 FAILED at 1302.
Hunk #3 FAILED at 1319.
Hunk #4 succeeded at 1359 (offset -41 lines).
3 out of 4 hunks FAILED -- saving rejects to file drivers/net/sfc/sfc_flow.c.rej
patching file drivers/net/sfc/sfc_rx.c
patching file drivers/net/sfc/sfc_rx.h

Repo: dpdk-next-crypto
37433:
patching file drivers/net/sfc/sfc.c
Hunk #1 succeeded at 638 (offset 60 lines).
Hunk #2 succeeded at 663 (offset 60 lines).
Hunk #3 succeeded at 688 (offset 60 lines).
Hunk #4 succeeded at 751 (offset 60 lines).
Hunk #5 succeeded at 770 (offset 60 lines).
Hunk #6 succeeded at 804 (offset 60 lines).
patching file drivers/net/sfc/sfc.h
patching file drivers/net/sfc/sfc_ethdev.c
Hunk #1 succeeded at 153 (offset -1 lines).
Hunk #2 succeeded at 1384 (offset 10 lines).
Hunk #3 succeeded at 1424 (offset 10 lines).
Hunk #4 succeeded at 1461 (offset 10 lines).
patching file drivers/net/sfc/sfc_flow.c
Hunk #1 FAILED at 1268.
Hunk #2 FAILED at 1302.
Hunk #3 FAILED at 1319.
Hunk #4 succeeded at 1359 (offset -41 lines).
3 out of 4 hunks FAILED -- saving rejects to file drivers/net/sfc/sfc_flow.c.rej
patching file drivers/net/sfc/sfc_rx.c
patching file drivers/net/sfc/sfc_rx.h

Repo: dpdk-next-net
37433:
patching file drivers/net/sfc/sfc.c
Hunk #1 succeeded at 638 (offset 60 lines).
Hunk #2 succeeded at 663 with fuzz 1 (offset 60 lines).
Hunk #3 succeeded at 690 (offset 62 lines).
Hunk #4 succeeded at 753 (offset 62 lines).
Hunk #5 succeeded at 772 (offset 62 lines).
Hunk #6 succeeded at 806 (offset 62 lines).
patching file drivers/net/sfc/sfc.h
patching file drivers/net/sfc/sfc_ethdev.c
Hunk #1 succeeded at 153 (offset -1 lines).
Hunk #2 succeeded at 1384 (offset 10 lines).
Hunk #3 succeeded at 1424 (offset 10 lines).
Hunk #4 succeeded at 1461 (offset 10 lines).
patching file drivers/net/sfc/sfc_flow.c
Hunk #1 FAILED at 1268.
Hunk #2 FAILED at 1302.
Hunk #3 FAILED at 1319.
Hunk #4 succeeded at 1359 (offset -41 lines).
3 out of 4 hunks FAILED -- saving rejects to file drivers/net/sfc/sfc_flow.c.rej
patching file drivers/net/sfc/sfc_rx.c
patching file drivers/net/sfc/sfc_rx.h

Repo: dpdk-next-virtio
37433:
patching file drivers/net/sfc/sfc.c
Hunk #1 succeeded at 638 (offset 60 lines).
Hunk #2 succeeded at 663 (offset 60 lines).
Hunk #3 succeeded at 688 (offset 60 lines).
Hunk #4 succeeded at 751 (offset 60 lines).
Hunk #5 succeeded at 770 (offset 60 lines).
Hunk #6 succeeded at 804 (offset 60 lines).
patching file drivers/net/sfc/sfc.h
patching file drivers/net/sfc/sfc_ethdev.c
Hunk #1 succeeded at 153 (offset -1 lines).
Hunk #2 succeeded at 1384 (offset 10 lines).
Hunk #3 succeeded at 1424 (offset 10 lines).
Hunk #4 succeeded at 1461 (offset 10 lines).
patching file drivers/net/sfc/sfc_flow.c
Hunk #1 FAILED at 1268.
Hunk #2 FAILED at 1302.
Hunk #3 FAILED at 1319.
Hunk #4 succeeded at 1359 (offset -41 lines).
3 out of 4 hunks FAILED -- saving rejects to file drivers/net/sfc/sfc_flow.c.rej
patching file drivers/net/sfc/sfc_rx.c
patching file drivers/net/sfc/sfc_rx.h

Repo: dpdk-next-eventdev
37433:
patching file drivers/net/sfc/sfc.c
patching file drivers/net/sfc/sfc.h
patching file drivers/net/sfc/sfc_ethdev.c
patching file drivers/net/sfc/sfc_flow.c
Hunk #1 FAILED at 1268.
Hunk #2 FAILED at 1302.
Hunk #3 FAILED at 1319.
Hunk #4 succeeded at 1359 (offset -41 lines).
3 out of 4 hunks FAILED -- saving rejects to file drivers/net/sfc/sfc_flow.c.rej
patching file drivers/net/sfc/sfc_rx.c
patching file drivers/net/sfc/sfc_rx.h


DPDK STV team

                 reply	other threads:[~2018-04-18 15: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='f7a79a$1hbt8n@orsmga002.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=arybchenko@solarflare.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).