From: sys_stv@intel.com
To: test-report@dpdk.org, ruifeng.wang@arm.com
Subject: [dpdk-test-report] |WARNING| pw(116868) sid(24828) job(PER_PATCH_BUILD4336)[2/2] crypto/armv8: adapt to updated sym session framework
Date: 26 Sep 2022 03:23:39 -0700 [thread overview]
Message-ID: <ea6bce$iid2ts@fmsmga007-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1678 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/116868
_apply issues_
Submitter: Ruifeng Wang <ruifeng.wang@arm.com>
Date: 2022-09-26 10:01:20
Reply_mail: <20220926100120.3980185-3-ruifeng.wang@arm.com>
DPDK git baseline:
Repo:dpdk-next-crypto, CommitID: cddc115bc024789d593cf2cad613fc85e08cfa3b
Repo:dpdk, CommitID: 479c2b1b5f9241c95d373b6c0c7bff8710096ee3
* Repo: dpdk-next-crypto
Server version missing
You should provide the server version in the URL configured via git-config or --server
This will be required in git-pw 2.0
error: patch failed: app/test/test_cryptodev.c:2176
error: app/test/test_cryptodev.c: patch does not apply
Applying: test/crypto: fix unexpected test abort
Patch failed at 0001 test/crypto: fix unexpected test abort
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".
* Repo: dpdk
Server version missing
You should provide the server version in the URL configured via git-config or --server
This will be required in git-pw 2.0
error: patch failed: app/test/test_cryptodev.c:2176
error: app/test/test_cryptodev.c: patch does not apply
Applying: test/crypto: fix unexpected test abort
Patch failed at 0001 test/crypto: fix unexpected test abort
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-09-26 10: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='ea6bce$iid2ts@fmsmga007-auth.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=ruifeng.wang@arm.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).