automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: motih@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw34079 [PATCH v4] net/failsafe: add Rx interrupts
Date: 21 Jan 2018 16:45:03 -0800	[thread overview]
Message-ID: <f7a79a$qvj8v@orsmga002.jf.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Moti Haimovsky <motih@mellanox.com>
Date: Fri, 19 Jan 2018 11:32:24 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:18daa7305ffd89b443cf56694fd30790cca0d3ce
                   Repo:dpdk-next-crypto, Branch:master, CommitID:a1472935a8b81a328ed8d6f553ee2523fea96757
                   Repo:dpdk-next-net, Branch:master, CommitID:bd03df964cb73fa7ec0bc4053f3a4214b0adc9e3
                   Repo:dpdk-next-virtio, Branch:master, CommitID:dd854ceec2e09a93f2509de03ae6d67e201b1a2b
                   Repo:dpdk, Branch:master, CommitID:ae80146c5a1ba8ddab686d4bc2e4663e78677457
                   
Apply patch file failed:
Repo: dpdk
34079:
patching file doc/guides/nics/features/failsafe.ini
patching file drivers/net/failsafe/Makefile
patching file drivers/net/failsafe/failsafe.c
Hunk #1 succeeded at 244 (offset -7 lines).
patching file drivers/net/failsafe/failsafe_ether.c
patching file drivers/net/failsafe/failsafe_intr.c
patching file drivers/net/failsafe/failsafe_ops.c
Hunk #1 succeeded at 33 with fuzz 2 (offset 1 line).
Hunk #2 succeeded at 200 (offset 39 lines).
Hunk #3 succeeded at 214 (offset 39 lines).
Hunk #4 succeeded at 235 (offset 39 lines).
Hunk #5 succeeded at 329 (offset 58 lines).
Hunk #6 succeeded at 347 (offset 58 lines).
Hunk #7 succeeded at 392 (offset 70 lines).
Hunk #8 succeeded at 920 (offset 113 lines).
patching file drivers/net/failsafe/failsafe_private.h
Hunk #1 succeeded at 40 with fuzz 1.
Hunk #2 succeeded at 61 (offset -1 lines).
Hunk #3 succeeded at 76 (offset -1 lines).
Hunk #4 FAILED at 170.
Hunk #5 succeeded at 180 (offset -2 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/failsafe/failsafe_private.h.rej

Repo: dpdk-next-crypto
34079:
patching file doc/guides/nics/features/failsafe.ini
patching file drivers/net/failsafe/Makefile
patching file drivers/net/failsafe/failsafe.c
Hunk #1 succeeded at 244 (offset -7 lines).
patching file drivers/net/failsafe/failsafe_ether.c
patching file drivers/net/failsafe/failsafe_intr.c
patching file drivers/net/failsafe/failsafe_ops.c
Hunk #2 succeeded at 159 (offset -2 lines).
Hunk #3 FAILED at 175.
Hunk #4 succeeded at 186 (offset -5 lines).
Hunk #5 succeeded at 261 (offset -5 lines).
Hunk #6 succeeded at 279 (offset -5 lines).
Hunk #7 succeeded at 312 (offset -5 lines).
Hunk #8 succeeded at 789 (offset -13 lines).
1 out of 8 hunks FAILED -- saving rejects to file drivers/net/failsafe/failsafe_ops.c.rej
patching file drivers/net/failsafe/failsafe_private.h
Hunk #1 succeeded at 40 with fuzz 1.
Hunk #2 succeeded at 58 with fuzz 2 (offset -4 lines).
Hunk #3 succeeded at 73 (offset -4 lines).
Hunk #4 FAILED at 170.
Hunk #5 succeeded at 175 (offset -7 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/failsafe/failsafe_private.h.rej

Repo: dpdk-next-net
34079:
patching file doc/guides/nics/features/failsafe.ini
patching file drivers/net/failsafe/Makefile
patching file drivers/net/failsafe/failsafe.c
Hunk #1 succeeded at 244 (offset -7 lines).
patching file drivers/net/failsafe/failsafe_ether.c
patching file drivers/net/failsafe/failsafe_intr.c
patching file drivers/net/failsafe/failsafe_ops.c
Hunk #1 succeeded at 33 with fuzz 2 (offset 1 line).
Hunk #2 succeeded at 200 (offset 39 lines).
Hunk #3 succeeded at 214 (offset 39 lines).
Hunk #4 succeeded at 235 (offset 39 lines).
Hunk #5 succeeded at 329 (offset 58 lines).
Hunk #6 succeeded at 347 (offset 58 lines).
Hunk #7 succeeded at 392 (offset 70 lines).
Hunk #8 succeeded at 920 (offset 113 lines).
patching file drivers/net/failsafe/failsafe_private.h
Hunk #1 succeeded at 40 with fuzz 1.
Hunk #2 succeeded at 61 (offset -1 lines).
Hunk #3 succeeded at 76 (offset -1 lines).
Hunk #4 FAILED at 170.
Hunk #5 succeeded at 180 (offset -2 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/failsafe/failsafe_private.h.rej

Repo: dpdk-next-virtio
34079:
patching file doc/guides/nics/features/failsafe.ini
patching file drivers/net/failsafe/Makefile
patching file drivers/net/failsafe/failsafe.c
Hunk #1 succeeded at 244 (offset -7 lines).
patching file drivers/net/failsafe/failsafe_ether.c
patching file drivers/net/failsafe/failsafe_intr.c
patching file drivers/net/failsafe/failsafe_ops.c
Hunk #1 succeeded at 33 with fuzz 2 (offset 1 line).
Hunk #2 succeeded at 178 (offset 17 lines).
Hunk #3 FAILED at 175.
Hunk #4 succeeded at 205 (offset 14 lines).
Hunk #5 succeeded at 299 (offset 33 lines).
Hunk #6 succeeded at 317 (offset 33 lines).
Hunk #7 succeeded at 362 (offset 45 lines).
Hunk #8 succeeded at 882 (offset 80 lines).
1 out of 8 hunks FAILED -- saving rejects to file drivers/net/failsafe/failsafe_ops.c.rej
patching file drivers/net/failsafe/failsafe_private.h
Hunk #1 succeeded at 40 with fuzz 1.
Hunk #2 succeeded at 58 with fuzz 2 (offset -4 lines).
Hunk #3 succeeded at 73 (offset -4 lines).
Hunk #4 FAILED at 170.
Hunk #5 succeeded at 175 (offset -7 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/failsafe/failsafe_private.h.rej

Repo: dpdk-next-eventdev
34079:
patching file doc/guides/nics/features/failsafe.ini
patching file drivers/net/failsafe/Makefile
patching file drivers/net/failsafe/failsafe.c
Hunk #1 succeeded at 244 (offset -7 lines).
patching file drivers/net/failsafe/failsafe_ether.c
patching file drivers/net/failsafe/failsafe_intr.c
patching file drivers/net/failsafe/failsafe_ops.c
Hunk #2 succeeded at 159 (offset -2 lines).
Hunk #3 FAILED at 175.
Hunk #4 succeeded at 186 (offset -5 lines).
Hunk #5 succeeded at 261 (offset -5 lines).
Hunk #6 succeeded at 279 (offset -5 lines).
Hunk #7 succeeded at 312 (offset -5 lines).
Hunk #8 succeeded at 789 (offset -13 lines).
1 out of 8 hunks FAILED -- saving rejects to file drivers/net/failsafe/failsafe_ops.c.rej
patching file drivers/net/failsafe/failsafe_private.h
Hunk #1 succeeded at 40 with fuzz 1.
Hunk #2 succeeded at 58 with fuzz 2 (offset -4 lines).
Hunk #3 succeeded at 73 (offset -4 lines).
Hunk #4 FAILED at 170.
Hunk #5 succeeded at 175 (offset -7 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/failsafe/failsafe_private.h.rej


DPDK STV team

                 reply	other threads:[~2018-01-22  0:45 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$qvj8v@orsmga002.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=motih@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).