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| pw33273 [PATCH v2 2/6] net/sfc: make Tx free threshold check datapath specific
Date: 15 Jan 2018 13:05:14 -0800	[thread overview]
Message-ID: <b11803$ai9rk@fmsmga002.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Andrew Rybchenko <arybchenko@solarflare.com>
Date: Tue, 9 Jan 2018 20:24:52 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:18280212534a7dcb61021393afd7394eaa1ff51e
                   Repo:dpdk-next-crypto, Branch:master, CommitID:95415cfefead276dff18262c9d96df73ecb3a8de
                   Repo:dpdk-next-net, Branch:master, CommitID:fb79a5525fb9d1979654f508c197a4f6186fcaaa
                   Repo:dpdk-next-virtio, Branch:master, CommitID:814339ba7eea13d132508af2cccec2f73568e2d0
                   Repo:dpdk, Branch:master, CommitID:4f438c85153ef7e910917c38ad60c0b6f296ee2d
                   
Apply patch file failed:
Repo: dpdk-next-net
33273:
patching file drivers/net/sfc/sfc_dp_tx.h
Hunk #1 succeeded at 81 with fuzz 1 (offset 3 lines).
Hunk #2 FAILED at 160.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/sfc/sfc_dp_tx.h.rej
patching file drivers/net/sfc/sfc_ef10_tx.c
Hunk #1 succeeded at 494 with fuzz 2 (offset 7 lines).
Hunk #2 FAILED at 641.
Hunk #3 FAILED at 657.
2 out of 3 hunks FAILED -- saving rejects to file drivers/net/sfc/sfc_ef10_tx.c.rej
patching file drivers/net/sfc/sfc_tx.c
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
8 out of 8 hunks ignored -- saving rejects to file drivers/net/sfc/sfc_tx.c.rej


DPDK STV team

                 reply	other threads:[~2018-01-15 21:05 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='b11803$ai9rk@fmsmga002.fm.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).