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| pw138378 [PATCH] net/mlx5: fix next L3 protocol fetching
Date: Thu, 14 Mar 2024 05:27:53 -0700 (PDT)	[thread overview]
Message-ID: <65f2ed49.050a0220.7ef46.1ae0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240314105902.399968-1-dsosnowski@nvidia.com>

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

_apply patch failure_

Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Thursday, March 14 2024 10:59:02 
Applied on: CommitID:cd218549b686d6be394ef3b171eafa16c038bfe3
Apply patch set 138378 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 (cd218549b686d6be394ef3b171eafa16c038bfe3)
Done: main commit cd218549b686d6be394ef3b171eafa16c038bfe3
Trying to checkout branch: origin/next-net-mlx-for-next-net
Checked out to next-net-mlx-for-next-net (1585a8ddae09ea651ec0bfd462783b71b90534ab)
Applying patch...

Failed to apply patch:
Applying: net/mlx5: fix next L3 protocol fetching
error: sha1 information is lacking or useless (drivers/net/mlx5/mlx5_flow_dv.c).
error: could not build fake ancestor
hint: Use 'git am --show-current-patch' to see the failed patch
Patch failed at 0001 net/mlx5: fix next L3 protocol fetching
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 (cd218549b686d6be394ef3b171eafa16c038bfe3)
Applying patch...

Failed to apply patch:
Applying: net/mlx5: fix next L3 protocol fetching
error: sha1 information is lacking or useless (drivers/net/mlx5/mlx5_flow_dv.c).
error: could not build fake ancestor
hint: Use 'git am --show-current-patch' to see the failed patch
Patch failed at 0001 net/mlx5: fix next L3 protocol fetching
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/29549/

UNH-IOL DPDK Community Lab

      parent reply	other threads:[~2024-03-14 12:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240314105902.399968-1-dsosnowski@nvidia.com>
2024-03-14 10:38 ` |SUCCESS| " qemudev
2024-03-14 10:43 ` qemudev
2024-03-14 11:01 ` checkpatch
2024-03-14 12:27 ` 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=65f2ed49.050a0220.7ef46.1ae0SMTPIN_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).