From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: nelio.laranjeiro@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw32282 [PATCH v4 2/3] examples/ipsec-secgw: add target queues in flow actions
Date: 25 Dec 2017 19:08:31 -0800 [thread overview]
Message-ID: <b11803$4jrhj@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2208 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/32282
_apply patch file failure_
Submitter: =?utf-8?q?N=C3=A9lio_Laranjeiro?= <nelio.laranjeiro@6wind.com>
Date: Thu, 14 Dec 2017 16:14:10 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:36d020c107ba65a584784a3f52484ea1698d4f9d
Repo:dpdk-next-crypto, Branch:master, CommitID:b8cde08731e9f6a7b250a7c5b10212bf009659a4
Repo:dpdk-next-net, Branch:master, CommitID:929a80374047dacd785c42db8e240901af041e9a
Repo:dpdk-next-virtio, Branch:master, CommitID:4f761c94b520ce71c56be1c913e54a4179b81c43
Repo:dpdk, Branch:master, CommitID:91a0eabf00cbd78a8630ff1b9279af1b2db92122
Apply patch file failed:
Repo: dpdk
32282:
patching file examples/ipsec-secgw/ipsec.c
Hunk #1 succeeded at 135 (offset -7 lines).
Hunk #2 FAILED at 202.
1 out of 2 hunks FAILED -- saving rejects to file examples/ipsec-secgw/ipsec.c.rej
patching file examples/ipsec-secgw/ipsec.h
Repo: dpdk-next-crypto
32282:
patching file examples/ipsec-secgw/ipsec.c
Hunk #1 succeeded at 135 (offset -7 lines).
Hunk #2 FAILED at 202.
1 out of 2 hunks FAILED -- saving rejects to file examples/ipsec-secgw/ipsec.c.rej
patching file examples/ipsec-secgw/ipsec.h
Repo: dpdk-next-net
32282:
patching file examples/ipsec-secgw/ipsec.c
Hunk #1 succeeded at 135 (offset -7 lines).
Hunk #2 FAILED at 202.
1 out of 2 hunks FAILED -- saving rejects to file examples/ipsec-secgw/ipsec.c.rej
patching file examples/ipsec-secgw/ipsec.h
Repo: dpdk-next-virtio
32282:
patching file examples/ipsec-secgw/ipsec.c
Hunk #1 FAILED at 142.
Hunk #2 FAILED at 201.
2 out of 2 hunks FAILED -- saving rejects to file examples/ipsec-secgw/ipsec.c.rej
patching file examples/ipsec-secgw/ipsec.h
Hunk #1 FAILED at 133.
1 out of 1 hunk FAILED -- saving rejects to file examples/ipsec-secgw/ipsec.h.rej
Repo: dpdk-next-eventdev
32282:
patching file examples/ipsec-secgw/ipsec.c
Hunk #1 succeeded at 135 (offset -7 lines).
Hunk #2 FAILED at 202.
1 out of 2 hunks FAILED -- saving rejects to file examples/ipsec-secgw/ipsec.c.rej
patching file examples/ipsec-secgw/ipsec.h
DPDK STV team
reply other threads:[~2017-12-26 3:08 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$4jrhj@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=nelio.laranjeiro@6wind.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).