automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: radu.nicolau@intel.com
Subject: [dpdk-test-report] |FAILURE| pw27990 [PATCH RFC 5/5] examples/ipsec-secgw: enabled inline ipsec
Date: 25 Aug 2017 09:57:20 -0700	[thread overview]
Message-ID: <8a7c36$12o3rbk@orsmga001.jf.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Radu Nicolau <radu.nicolau@intel.com>
Date: Fri, 25 Aug 2017 15:57:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:85238f501ec36bc6f0e15e6434296312841259bd
                   Repo:dpdk-next-crypto, Branch:master, CommitID:85238f501ec36bc6f0e15e6434296312841259bd
                   Repo:dpdk-next-net, Branch:master, CommitID:729fab783ca0b6a44281112285d58250b459ba09
                   Repo:dpdk-next-virtio, Branch:master, CommitID:6c157fe64650167646ff1312f9f7e7dc3674d7eb
                   Repo:dpdk, Branch:master, CommitID:85238f501ec36bc6f0e15e6434296312841259bd
                   
Apply patch file failed:
Repo: dpdk
27990:
patching file examples/ipsec-secgw/esp.c
patching file examples/ipsec-secgw/ipsec.c
Hunk #1 succeeded at 57 (offset -1 lines).
Hunk #2 FAILED at 83.
Hunk #3 succeeded at 130 with fuzz 2 (offset -20 lines).
Hunk #4 FAILED at 207.
Hunk #5 succeeded at 187 (offset -46 lines).
2 out of 5 hunks FAILED -- saving rejects to file examples/ipsec-secgw/ipsec.c.rej
patching file examples/ipsec-secgw/ipsec.h
Hunk #1 succeeded at 133 (offset -9 lines).
patching file examples/ipsec-secgw/sa.c
Hunk #1 succeeded at 567 (offset -46 lines).
Hunk #2 FAILED at 765.
Hunk #3 succeeded at 763 (offset -74 lines).
Hunk #4 succeeded at 776 (offset -74 lines).
Hunk #5 succeeded at 787 (offset -74 lines).
Hunk #6 succeeded at 800 (offset -74 lines).
Hunk #7 succeeded at 927 (offset -74 lines).
1 out of 7 hunks FAILED -- saving rejects to file examples/ipsec-secgw/sa.c.rej

Repo: dpdk-next-crypto
27990:
patching file examples/ipsec-secgw/esp.c
patching file examples/ipsec-secgw/ipsec.c
Hunk #1 succeeded at 57 (offset -1 lines).
Hunk #2 FAILED at 83.
Hunk #3 succeeded at 130 with fuzz 2 (offset -20 lines).
Hunk #4 FAILED at 207.
Hunk #5 succeeded at 187 (offset -46 lines).
2 out of 5 hunks FAILED -- saving rejects to file examples/ipsec-secgw/ipsec.c.rej
patching file examples/ipsec-secgw/ipsec.h
Hunk #1 succeeded at 133 (offset -9 lines).
patching file examples/ipsec-secgw/sa.c
Hunk #1 succeeded at 567 (offset -46 lines).
Hunk #2 FAILED at 765.
Hunk #3 succeeded at 763 (offset -74 lines).
Hunk #4 succeeded at 776 (offset -74 lines).
Hunk #5 succeeded at 787 (offset -74 lines).
Hunk #6 succeeded at 800 (offset -74 lines).
Hunk #7 succeeded at 927 (offset -74 lines).
1 out of 7 hunks FAILED -- saving rejects to file examples/ipsec-secgw/sa.c.rej

Repo: dpdk-next-net
27990:
patching file examples/ipsec-secgw/esp.c
patching file examples/ipsec-secgw/ipsec.c
Hunk #1 succeeded at 57 (offset -1 lines).
Hunk #2 FAILED at 83.
Hunk #3 succeeded at 130 with fuzz 2 (offset -20 lines).
Hunk #4 FAILED at 207.
Hunk #5 succeeded at 187 (offset -46 lines).
2 out of 5 hunks FAILED -- saving rejects to file examples/ipsec-secgw/ipsec.c.rej
patching file examples/ipsec-secgw/ipsec.h
Hunk #1 succeeded at 133 (offset -9 lines).
patching file examples/ipsec-secgw/sa.c
Hunk #1 succeeded at 567 (offset -46 lines).
Hunk #2 FAILED at 765.
Hunk #3 succeeded at 763 (offset -74 lines).
Hunk #4 succeeded at 776 (offset -74 lines).
Hunk #5 succeeded at 787 (offset -74 lines).
Hunk #6 succeeded at 800 (offset -74 lines).
Hunk #7 succeeded at 927 (offset -74 lines).
1 out of 7 hunks FAILED -- saving rejects to file examples/ipsec-secgw/sa.c.rej

Repo: dpdk-next-virtio
27990:
patching file examples/ipsec-secgw/esp.c
patching file examples/ipsec-secgw/ipsec.c
Hunk #1 succeeded at 57 (offset -1 lines).
Hunk #2 FAILED at 83.
Hunk #3 succeeded at 130 with fuzz 2 (offset -20 lines).
Hunk #4 FAILED at 207.
Hunk #5 succeeded at 187 (offset -46 lines).
2 out of 5 hunks FAILED -- saving rejects to file examples/ipsec-secgw/ipsec.c.rej
patching file examples/ipsec-secgw/ipsec.h
Hunk #1 succeeded at 133 (offset -9 lines).
patching file examples/ipsec-secgw/sa.c
Hunk #1 succeeded at 567 (offset -46 lines).
Hunk #2 FAILED at 765.
Hunk #3 succeeded at 763 (offset -74 lines).
Hunk #4 succeeded at 776 (offset -74 lines).
Hunk #5 succeeded at 787 (offset -74 lines).
Hunk #6 succeeded at 800 (offset -74 lines).
Hunk #7 succeeded at 927 (offset -74 lines).
1 out of 7 hunks FAILED -- saving rejects to file examples/ipsec-secgw/sa.c.rej

Repo: dpdk-next-eventdev
27990:
patching file examples/ipsec-secgw/esp.c
patching file examples/ipsec-secgw/ipsec.c
Hunk #1 succeeded at 57 (offset -1 lines).
Hunk #2 FAILED at 83.
Hunk #3 succeeded at 130 with fuzz 2 (offset -20 lines).
Hunk #4 FAILED at 207.
Hunk #5 succeeded at 187 (offset -46 lines).
2 out of 5 hunks FAILED -- saving rejects to file examples/ipsec-secgw/ipsec.c.rej
patching file examples/ipsec-secgw/ipsec.h
Hunk #1 succeeded at 133 (offset -9 lines).
patching file examples/ipsec-secgw/sa.c
Hunk #1 succeeded at 567 (offset -46 lines).
Hunk #2 FAILED at 765.
Hunk #3 succeeded at 763 (offset -74 lines).
Hunk #4 succeeded at 776 (offset -74 lines).
Hunk #5 succeeded at 787 (offset -74 lines).
Hunk #6 succeeded at 800 (offset -74 lines).
Hunk #7 succeeded at 927 (offset -74 lines).
1 out of 7 hunks FAILED -- saving rejects to file examples/ipsec-secgw/sa.c.rej


DPDK STV team

                 reply	other threads:[~2017-08-25 16:57 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='8a7c36$12o3rbk@orsmga001.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=radu.nicolau@intel.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).