From: sys_stv@intel.com
To: test-report@dpdk.org, vfialko@marvell.com
Subject: [dpdk-test-report] |WARNING| pw(112063) sid(23246) job(PER_PATCH_BUILD2737)app/test: add event inline security tests
Date: 30 May 2022 16:23:53 -0700 [thread overview]
Message-ID: <87f1b2$h5degf@orsmga007-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/112063
_apply issues_
Submitter: Volodymyr Fialko <vfialko@marvell.com>
Date: 2022-05-30 13:39:06
Reply_mail: <20220530133906.1139270-1-vfialko@marvell.com>
DPDK git baseline:
Repo:dpdk, CommitID: 60018ef4d33d5d3e1e9995945ec33a07e75784a4
* Repo: dpdk
Starting new HTTP connection (1): proxy-prc.intel.com
error: app/test/test_security_inline_proto.c: does not exist in index
Applying: app/test: add event inline security tests
Patch failed at 0001 app/test: add event inline security tests
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-05-30 23:23 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='87f1b2$h5degf@orsmga007-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=vfialko@marvell.com \
/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).