From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw111341 [PATCH] [v2] examples/fips_validation: reset IV generation in every test group
Date: Thu, 19 May 2022 03:08:22 -0400 (EDT) [thread overview]
Message-ID: <20220519070822.10BD06D3A7@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/111341
_apply patch failure_
Submitter: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: Thursday, May 19 2022 06:08:34
Applied on: CommitID:68c050954ff393b894aa3672a5ef1a231597dab0
Apply patch set 111341 failed:
Checking patch examples/fips_validation/fips_validation_gcm.c...
error: while searching for:
direction_obj = json_object_get(json_info.json_test_group, DIR_JSON_STR);
direction_str = json_string_value(direction_obj);
if (strcmp(direction_str, OP_ENC_JSON_STR) == 0) {
json_t *ivGen_obj = json_object_get(json_info.json_test_group, IVGEN_JSON_STR);
error: patch failed: examples/fips_validation/fips_validation_gcm.c:344
Applying patch examples/fips_validation/fips_validation_gcm.c with 1 reject...
Rejected hunk #1.
diff a/examples/fips_validation/fips_validation_gcm.c b/examples/fips_validation/fips_validation_gcm.c (rejected hunks)
@@ -344,6 +344,7 @@ parse_test_gcm_json_init(void)
direction_obj = json_object_get(json_info.json_test_group, DIR_JSON_STR);
direction_str = json_string_value(direction_obj);
+ info.interim_info.gcm_data.gen_iv = 0;
if (strcmp(direction_str, OP_ENC_JSON_STR) == 0) {
json_t *ivGen_obj = json_object_get(json_info.json_test_group, IVGEN_JSON_STR);
https://lab.dpdk.org/results/dashboard/patchsets/22180/
UNH-IOL DPDK Community Lab
reply other threads:[~2022-05-19 7: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=20220519070822.10BD06D3A7@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).