automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw153807-153813 [PATCH] [v4, 7/7] net/ena: upgrade driver version to 2.13.0
Date: Thu, 29 May 2025 06:52:42 -0700 (PDT)	[thread overview]
Message-ID: <683866aa.170a0220.2c483d.490bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250528102806.10030-1-shaibran@amazon.com>

Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/153813

_apply patch failure_

Submitter: Shai Brandes <shaibran@amazon.com>
Date: Wednesday, May 28 2025 10:28:06 
Applied on: CommitID:a633a128fd09ff1fc72312f4e4d1a9e0f73aa359
Apply patch set 153807-153813 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 (a633a128fd09ff1fc72312f4e4d1a9e0f73aa359)
Done: main commit a633a128fd09ff1fc72312f4e4d1a9e0f73aa359
Trying to checkout branch: origin/next-net-for-main
Checked out to next-net-for-main (466db466e2938c0d4e7f3dd75435483133f98770)
Applying patch...

Failed to apply patch:
Applying: net/ena/base: avoid recalculating desc per entry
Applying: net/ena/base: coding style changes
Applying: net/ena: separate doorbell logic for Rx and Tx
Applying: net/ena: support fragment bypass mode
Using index info to reconstruct a base tree...
M	doc/guides/rel_notes/release_25_07.rst
Falling back to patching base and 3-way merge...
Auto-merging doc/guides/rel_notes/release_25_07.rst
CONFLICT (content): Merge conflict in doc/guides/rel_notes/release_25_07.rst
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0004 net/ena: support fragment bypass mode
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".


Trying to checkout branch: origin/main
Checked out to main (a633a128fd09ff1fc72312f4e4d1a9e0f73aa359)
Applying patch...

Failed to apply patch:
Applying: net/ena/base: avoid recalculating desc per entry
Applying: net/ena/base: coding style changes
Applying: net/ena: separate doorbell logic for Rx and Tx
Applying: net/ena: support fragment bypass mode
Using index info to reconstruct a base tree...
M	doc/guides/rel_notes/release_25_07.rst
Falling back to patching base and 3-way merge...
Auto-merging doc/guides/rel_notes/release_25_07.rst
CONFLICT (content): Merge conflict in doc/guides/rel_notes/release_25_07.rst
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0004 net/ena: support fragment bypass mode
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/33265/

UNH-IOL DPDK Community Lab

      parent reply	other threads:[~2025-05-29 13:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250528102806.10030-1-shaibran@amazon.com>
2025-05-28 10:10 ` |SUCCESS| pw153807-153813 [PATCH v4 " qemudev
2025-05-28 10:14 ` qemudev
2025-05-28 10:28 ` |WARNING| pw153813 " checkpatch
2025-05-28 11:44 ` |SUCCESS| " 0-day Robot
2025-05-29 13:52 ` 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=683866aa.170a0220.2c483d.490bSMTPIN_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).