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| pw154628 [PATCH] [v2] bus/pci: fix automatic interrupt type selection
Date: Fri, 20 Jun 2025 07:53:28 -0700 (PDT)	[thread overview]
Message-ID: <685575e8.170a0220.2c1293.58daSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <d612fb276b9c8b173a5e476ca75b0460@iki.fi>

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

_apply patch failure_

Submitter: Pekka Riikonen <priikone@iki.fi>
Date: Friday, June 20 2025 12:50:27 
Applied on: CommitID:6890ee7ba76e92745d6c61b3b6b9d757ebaaa89d
Apply patch set 154628 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 (6890ee7ba76e92745d6c61b3b6b9d757ebaaa89d)
Done: main commit 6890ee7ba76e92745d6c61b3b6b9d757ebaaa89d
Trying to checkout branch: origin/main
Checked out to main (6890ee7ba76e92745d6c61b3b6b9d757ebaaa89d)
Applying patch...

Failed to apply patch:
Applying: bus/pci: fix automatic interrupt type selection
error: git diff header lacks filename information when removing 1 leading pathname component (line 8)
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 bus/pci: fix automatic interrupt type selection
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/33474/

UNH-IOL DPDK Community Lab

      parent reply	other threads:[~2025-06-20 14:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d612fb276b9c8b173a5e476ca75b0460@iki.fi>
2025-06-20 12:22 ` |WARNING| pw154628 [PATCH v2] " qemudev
2025-06-20 12:50 ` checkpatch
2025-06-20 14:53 ` 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=685575e8.170a0220.2c1293.58daSMTPIN_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).