From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw155484-155496 [PATCH] [v7, 13/13] eal: add warnings about ignored options
Date: Thu, 18 Sep 2025 11:11:58 -0700 (PDT) [thread overview]
Message-ID: <68cc4b6e.050a0220.30a7e6.a6ebSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250723162013.2392-14-bruce.richardson@intel.com>
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/155496
_apply patch failure_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Wednesday, July 23 2025 16:20:11
Applied on: CommitID:6e6cc1dc3548fc862cea377c98d7feef1a335468
Apply patch set 155484-155496 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 (6e6cc1dc3548fc862cea377c98d7feef1a335468)
Done: main commit 6e6cc1dc3548fc862cea377c98d7feef1a335468
Trying to checkout branch: origin/main
Checked out to main (6e6cc1dc3548fc862cea377c98d7feef1a335468)
Applying patch...
Failed to apply patch:
Applying: build: add define for the OS environment name
Applying: argparse: export function to print help text for object
Applying: argparse: allow user-override of help printing
Using index info to reconstruct a base tree...
M doc/guides/rel_notes/release_25_11.rst
Falling back to patching base and 3-way merge...
Auto-merging doc/guides/rel_notes/release_25_11.rst
CONFLICT (content): Merge conflict in doc/guides/rel_notes/release_25_11.rst
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0003 argparse: allow user-override of help printing
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/33741/
UNH-IOL DPDK Community Lab
prev parent reply other threads:[~2025-09-18 18:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250723162013.2392-14-bruce.richardson@intel.com>
2025-07-23 15:47 ` |SUCCESS| pw155484-155496 [PATCH v7 " qemudev
2025-07-23 15:52 ` qemudev
2025-07-23 16:22 ` |SUCCESS| pw155496 " checkpatch
2025-07-23 17:20 ` |SUCCESS| pw155484-155496 [PATCH] [v7,13/13] eal: add warnings about dpdklab
2025-07-23 17:30 ` dpdklab
2025-07-23 17:52 ` dpdklab
2025-07-23 18:06 ` dpdklab
2025-07-23 18:08 ` dpdklab
2025-07-23 18:09 ` dpdklab
2025-07-23 18:27 ` |PENDING| " dpdklab
2025-07-23 18:30 ` dpdklab
2025-07-23 18:34 ` |SUCCESS| " dpdklab
2025-07-23 18:43 ` |SUCCESS| pw155496 [PATCH v7 13/13] eal: add warnings about ignored options 0-day Robot
2025-07-23 18:46 ` |SUCCESS| pw155484-155496 [PATCH] [v7,13/13] eal: add warnings about dpdklab
2025-07-23 19:23 ` dpdklab
2025-07-23 20:13 ` dpdklab
2025-07-23 20:30 ` dpdklab
2025-07-23 20:32 ` |FAILURE| " dpdklab
2025-07-23 21:52 ` |WARNING| " dpdklab
2025-07-24 3:19 ` |SUCCESS| " dpdklab
2025-07-24 6:03 ` dpdklab
2025-07-24 6:05 ` dpdklab
2025-07-24 8:13 ` dpdklab
2025-08-29 14:06 ` |SUCCESS| pw155484-155496 [PATCH v7 13/13] eal: add warnings about ignored options qemudev
2025-08-29 14:14 ` |FAILURE| " qemudev
2025-08-29 14:38 ` |SUCCESS| " qemudev
2025-08-29 14:42 ` qemudev
2025-09-18 18:11 ` 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=68cc4b6e.050a0220.30a7e6.a6ebSMTPIN_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).