From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw156309-156314 [PATCH] [RFC, 6/6] ethdev: move mq_mode to [r, t]x_adv_conf
Date: Sat, 30 Aug 2025 10:31:31 -0700 (PDT) [thread overview]
Message-ID: <68b33573.d40a0220.2b542e.55b9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250830171706.428977-7-vladimir.medvedkin@intel.com>
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/156314
_apply patch failure_
Submitter: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Date: Saturday, August 30 2025 17:17:06
Applied on: CommitID:4a04a346e7f3aa68b7a272d05c86fec2e7db8e89
Apply patch set 156309-156314 failed:
Cloning the DPDK mirror at: https://github.com/DPDK/dpdk.git (Attempt 1 of 3)
Trying to checkout branch: origin/main
Checked out to main (4a04a346e7f3aa68b7a272d05c86fec2e7db8e89)
Done: main commit 4a04a346e7f3aa68b7a272d05c86fec2e7db8e89
Trying to checkout branch: origin/main
Checked out to main (4a04a346e7f3aa68b7a272d05c86fec2e7db8e89)
Applying patch...
Failed to apply patch:
Applying: ethdev: extend and refactor DCB configuration
error: sha1 information is lacking or useless (drivers/net/intel/ice/ice_ethdev.c).
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 ethdev: extend and refactor DCB configuration
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".
https://lab.dpdk.org/results/dashboard/patchsets/33996/
UNH-IOL DPDK Community Lab
prev parent reply other threads:[~2025-08-30 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250830171706.428977-7-vladimir.medvedkin@intel.com>
2025-08-30 17:16 ` |SUCCESS| pw156314 [RFC PATCH " checkpatch
2025-08-30 17:31 ` dpdklab [this message]
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=68b33573.d40a0220.2b542e.55b9SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).