From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw110371-110377 [PATCH] [v5, 7/7] test/security: add inline IPsec IPv6 flow label cases
Date: Wed, 27 Apr 2022 14:59:28 -0400 (EDT) [thread overview]
Message-ID: <20220427185928.7D44CA77C@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1537 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/110371
_apply patch failure_
Submitter: Akhil Goyal <gakhil@marvell.com>
Date: Wednesday, April 27 2022 15:10:54
Applied on: CommitID:55ae8965bf8eecd5ebec36663bb0f36018abf64b
Apply patch set 110371-110377 failed:
Checking patch app/test/test_cryptodev_security_ipsec.c...
Hunk #1 succeeded at 444 (offset -51 lines).
Hunk #2 succeeded at 876 (offset -61 lines).
Hunk #3 succeeded at 903 (offset -61 lines).
Hunk #4 succeeded at 1115 (offset -66 lines).
Hunk #5 succeeded at 1147 (offset -66 lines).
Checking patch app/test/test_cryptodev_security_ipsec.h...
Hunk #1 succeeded at 68 (offset -5 lines).
error: while searching for:
bool antireplay;
enum df_flags df;
enum dscp_flags dscp;
bool dec_ttl_or_hop_limit;
bool ah;
};
error: patch failed: app/test/test_cryptodev_security_ipsec.h:92
Checking patch app/test/test_security_inline_proto.c...
Applied patch app/test/test_cryptodev_security_ipsec.c cleanly.
Applying patch app/test/test_cryptodev_security_ipsec.h with 1 reject...
Hunk #1 applied cleanly.
Rejected hunk #2.
Applied patch app/test/test_security_inline_proto.c cleanly.
diff a/app/test/test_cryptodev_security_ipsec.h b/app/test/test_cryptodev_security_ipsec.h (rejected hunks)
@@ -92,6 +101,7 @@ struct ipsec_test_flags {
bool antireplay;
enum df_flags df;
enum dscp_flags dscp;
+ enum flabel_flags flabel;
bool dec_ttl_or_hop_limit;
bool ah;
};
https://lab.dpdk.org/results/dashboard/patchsets/21937/
UNH-IOL DPDK Community Lab
reply other threads:[~2022-04-27 18: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=20220427185928.7D44CA77C@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).