From: sys_stv@intel.com
To: test-report@dpdk.org, luca.vizzarro@arm.com
Subject: compilation|WARNING| pw(148419) sid(33926) job(PER_PATCH_BUILD14120)[v4, 3/3] dts: add l2fwd test suite
Date: 13 Nov 2024 08:54:13 -0800 [thread overview]
Message-ID: <a5627d$2k778u@orviesa007-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1498 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/148419
_apply issues_
Submitter: Luca Vizzarro <luca.vizzarro@arm.com>
Date: 2024-11-13 16:25:17
Reply_mail: <20241113162518.643764-6-luca.vizzarro@arm.com>
DPDK git baseline:
Repo:dpdk-next-dts, CommitID: 4b5abe7ec1ed2d43a285599bbba23f62ac049d8f
Repo:dpdk, CommitID: b8d1d60fadc414321221843f3277445d8156c202
* Repo: dpdk-next-dts
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: dts/framework/test_suite.py:310
error: dts/framework/test_suite.py: patch does not apply
Applying: dts: allow to get multiple expected packets
Patch failed at 0001 dts: allow to get multiple expected packets
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
Applying: dts: allow to get multiple expected packets
Applying: dts: add l2fwd test suite
Applying: dts: add l2fwd test suite
Patch failed at 0003 dts: add l2fwd test suite
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:[~2024-11-13 16:54 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='a5627d$2k778u@orviesa007-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=luca.vizzarro@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).