From: sys_stv@intel.com
To: test-report@dpdk.org, yan.yanovsky@catonetworks.com
Subject: compilation|WARNING| pw(159211) sid(36858) job(PER_PATCH_BUILD17464)af_xdp kick_tx() Retries instead of endless loop
Date: 07 Dec 2025 08:33:17 -0800 [thread overview]
Message-ID: <f068ff$5uknlb@ORVIESA003-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/159211
_apply issues_
Submitter: Yan Yanovsky <yan.yanovsky@catonetworks.com>
Date: 2025-12-07 16:26:02
Reply_mail: <VI1PR03MB41446415FCAB2BF4FFB1E266F7A5A@VI1PR03MB4144.eurprd03.prod.outlook.com>
DPDK git baseline:
Repo:dpdk-next-net, CommitID: 80b3e9cad7599ce01f94cd6f8f966401a77e29c1
Repo:dpdk, CommitID: cd60dcd503b91956f966a1f6d595b35d256ac00f
* Repo: dpdk-next-net
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
Failed to apply patch:
Patch is empty.
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To record the empty patch as an empty commit, run "git am --allow-empty".
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
Failed to apply patch:
Patch is empty.
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To record the empty patch as an empty commit, run "git am --allow-empty".
To restore the original branch and stop patching, run "git am --abort".
DPDK STV team
next reply other threads:[~2025-12-07 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-07 16:33 sys_stv [this message]
2025-12-08 2:25 sys_stv
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='f068ff$5uknlb@ORVIESA003-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=yan.yanovsky@catonetworks.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).