automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: anoob.joseph@caviumnetworks.com
Subject: [dpdk-test-report] |FAILURE| pw31481 [PATCH 2/2] examples/ipsec-secgw: add support for inline protocol
Date: 20 Nov 2017 02:59:21 -0800	[thread overview]
Message-ID: <07cd09$4kg79@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Anoob Joseph <anoob.joseph@caviumnetworks.com>
Date: Mon, 20 Nov 2017 10:31:45 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:b96273bb75fbd99a9732aa4d49658a3525b225b0
                   Repo:dpdk-next-crypto, Branch:master, CommitID:d84aad650401a122cb75bd5811e49b03ef3dc49d
                   Repo:dpdk-next-net, Branch:master, CommitID:d84aad650401a122cb75bd5811e49b03ef3dc49d
                   Repo:dpdk-next-virtio, Branch:master, CommitID:4f761c94b520ce71c56be1c913e54a4179b81c43
                   Repo:dpdk, Branch:master, CommitID:d84aad650401a122cb75bd5811e49b03ef3dc49d
                   
Apply patch file failed:
Repo: dpdk
31481:
patching file examples/ipsec-secgw/esp.c
patching file examples/ipsec-secgw/ipsec-secgw.c
patching file examples/ipsec-secgw/ipsec.c
Hunk #2 FAILED at 116.
1 out of 5 hunks FAILED -- saving rejects to file examples/ipsec-secgw/ipsec.c.rej

Repo: dpdk-next-crypto
31481:
patching file examples/ipsec-secgw/esp.c
patching file examples/ipsec-secgw/ipsec-secgw.c
patching file examples/ipsec-secgw/ipsec.c
Hunk #2 FAILED at 116.
1 out of 5 hunks FAILED -- saving rejects to file examples/ipsec-secgw/ipsec.c.rej

Repo: dpdk-next-net
31481:
patching file examples/ipsec-secgw/esp.c
patching file examples/ipsec-secgw/ipsec-secgw.c
patching file examples/ipsec-secgw/ipsec.c
Hunk #2 FAILED at 116.
1 out of 5 hunks FAILED -- saving rejects to file examples/ipsec-secgw/ipsec.c.rej

Repo: dpdk-next-virtio
31481:
patching file examples/ipsec-secgw/esp.c
Hunk #1 FAILED at 178.
Hunk #2 FAILED at 474.
2 out of 2 hunks FAILED -- saving rejects to file examples/ipsec-secgw/esp.c.rej
patching file examples/ipsec-secgw/ipsec-secgw.c
Hunk #1 succeeded at 267 (offset 2 lines).
Hunk #2 succeeded at 435 (offset 2 lines).
patching file examples/ipsec-secgw/ipsec.c
Hunk #1 succeeded at 44 (offset -2 lines).
Hunk #2 FAILED at 116.
Hunk #3 FAILED at 125.
Hunk #4 FAILED at 227.
Hunk #5 FAILED at 344.
4 out of 5 hunks FAILED -- saving rejects to file examples/ipsec-secgw/ipsec.c.rej

Repo: dpdk-next-eventdev
31481:
patching file examples/ipsec-secgw/esp.c
Hunk #1 FAILED at 178.
Hunk #2 FAILED at 474.
2 out of 2 hunks FAILED -- saving rejects to file examples/ipsec-secgw/esp.c.rej
patching file examples/ipsec-secgw/ipsec-secgw.c
Hunk #1 succeeded at 267 (offset 2 lines).
Hunk #2 succeeded at 435 (offset 2 lines).
patching file examples/ipsec-secgw/ipsec.c
Hunk #1 succeeded at 44 (offset -2 lines).
Hunk #2 FAILED at 116.
Hunk #3 FAILED at 125.
Hunk #4 FAILED at 227.
Hunk #5 FAILED at 344.
4 out of 5 hunks FAILED -- saving rejects to file examples/ipsec-secgw/ipsec.c.rej


DPDK STV team

                 reply	other threads:[~2017-11-20 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='07cd09$4kg79@fmsmga001.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=anoob.joseph@caviumnetworks.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).