automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, gmuthukrishn@marvell.com
Subject: [dpdk-test-report] |WARNING| pw(114916) sid(24296) job(PER_PATCH_BUILD3823)[v1, 5/5] examples/fips_validation: add asymmetric validation
Date: 12 Aug 2022 05:31:57 -0700	[thread overview]
Message-ID: <b63a69$hb3ch4@orsmga006-auth.jf.intel.com> (raw)

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


Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/114916

_apply issues_

Submitter: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: 2022-08-12 11:57:20
Reply_mail: <31a74d94644fb768bc34c3c87241b1d2781c9497.1660304194.git.gmuthukrishn@marvell.com>

DPDK git baseline:
	Repo:dpdk, CommitID: 72206323a5dd3182b13f61b25a64abdddfee595c


* 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: examples/fips_validation/fips_validation.h:293
error: examples/fips_validation/fips_validation.h: patch does not apply
Applying: examples/fips_validation: fix parsing test group info
Applying: examples/fips_validation: add interim parse writeback
Applying: examples/fips_validation: add function to calculate SHA hash size
Patch failed at 0003 examples/fips_validation: add function to calculate SHA hash size
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-08-12 12:32 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='b63a69$hb3ch4@orsmga006-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=gmuthukrishn@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).