From: sys_stv@intel.com
To: test-report@dpdk.org, gakhil@marvell.com
Subject: [dpdk-test-report] |WARNING| pw(109766) sid(22532) job(PER_PATCH_BUILD2042)[v4, 10/10] test/security: add inline IPsec IPv6 flow label cases
Date: 16 Apr 2022 12:32:58 -0700 [thread overview]
Message-ID: <003cea$h49loh@orsmga008-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/109766
_apply issues_
Submitter: Akhil Goyal <gakhil@marvell.com>
Date: 2022-04-16 19:25:30
Reply_mail: <20220416192530.173895-11-gakhil@marvell.com>
DPDK git baseline:
Repo:dpdk, CommitID: 76076342ec8ef108a155938d46a88bb493fae60e
* Repo: dpdk
This will be required in git-pw 2.0
Starting new HTTP connection (1): proxy-prc.intel.com
Starting new HTTP connection (1): proxy-prc.intel.com
error: patch failed: app/test/test_cryptodev_security_ipsec.h:94
error: app/test/test_cryptodev_security_ipsec.h: patch does not apply
Applying: app/test: add unit cases for inline IPsec offload
Applying: test/security: add inline inbound IPsec cases
--
Applying: test/security: add inline IPsec SA soft expiry cases
Applying: test/security: add inline IPsec SA hard expiry cases
Applying: test/security: add inline IPsec IPv6 flow label cases
Patch failed at 0010 test/security: add inline IPsec IPv6 flow label cases
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
DPDK STV team
reply other threads:[~2022-04-16 19:33 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='003cea$h49loh@orsmga008-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=gakhil@marvell.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).