From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw152371-152372 [PATCH] [v5, 2/2] dts: add VF configuration and workflow
Date: Wed, 11 Jun 2025 13:43:18 -0700 (PDT) [thread overview]
Message-ID: <6849ea66.170a0220.1b036a.00a1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250313033611.1896695-3-probb@iol.unh.edu>
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/152372
_apply patch failure_
Submitter: Patrick Robb <probb@iol.unh.edu>
Date: Thursday, March 13 2025 03:36:11
Applied on: CommitID:391ecf83a80b92343b04a7afe622757dde766a8d
Apply patch set 152371-152372 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 (391ecf83a80b92343b04a7afe622757dde766a8d)
Done: main commit 391ecf83a80b92343b04a7afe622757dde766a8d
Trying to checkout branch: origin/main
Checked out to main (391ecf83a80b92343b04a7afe622757dde766a8d)
Applying patch...
Failed to apply patch:
Applying: dts: add OS abstractions for creating virtual functions
Using index info to reconstruct a base tree...
M dts/framework/testbed_model/linux_session.py
M dts/framework/testbed_model/os_session.py
Falling back to patching base and 3-way merge...
Auto-merging dts/framework/testbed_model/os_session.py
Auto-merging dts/framework/testbed_model/linux_session.py
CONFLICT (content): Merge conflict in dts/framework/testbed_model/linux_session.py
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 dts: add OS abstractions for creating virtual functions
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/32817/
UNH-IOL DPDK Community Lab
prev parent reply other threads:[~2025-06-11 20:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250313033611.1896695-3-probb@iol.unh.edu>
2025-03-13 3:40 ` |SUCCESS| pw152372 [PATCH v5 " checkpatch
2025-03-13 4:45 ` |SUCCESS| pw152371-152372 [PATCH] [v5,2/2] dts: add VF configuration dpdklab
2025-03-13 5:07 ` dpdklab
2025-03-13 5:52 ` dpdklab
2025-03-13 6:01 ` dpdklab
2025-03-13 6:45 ` dpdklab
2025-03-13 6:50 ` |PENDING| " dpdklab
2025-03-13 6:59 ` dpdklab
2025-03-13 7:13 ` |SUCCESS| " dpdklab
2025-03-13 7:19 ` |PENDING| " dpdklab
2025-03-13 7:28 ` |SUCCESS| " dpdklab
2025-03-13 7:35 ` dpdklab
2025-03-13 7:50 ` dpdklab
2025-03-13 8:50 ` |PENDING| " dpdklab
2025-03-13 9:21 ` |SUCCESS| " dpdklab
2025-03-13 9:39 ` dpdklab
2025-03-13 9:43 ` dpdklab
2025-03-13 10:20 ` dpdklab
2025-03-13 10:42 ` dpdklab
2025-03-13 13:15 ` dpdklab
2025-03-13 13:23 ` dpdklab
2025-03-13 13:48 ` dpdklab
2025-06-11 20:43 ` 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=6849ea66.170a0220.1b036a.00a1SMTPIN_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).