From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw159029 [PATCH] [RFC] pcapng: improve performance of timestamping
Date: Tue, 25 Nov 2025 22:52:20 -0800 (PST) [thread overview]
Message-ID: <6926a3a4.050a0220.250248.eb29SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251126051218.50568-1-stephen@networkplumber.org>
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/159029
_apply patch failure_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, November 26 2025 05:12:18
Applied on: CommitID:2815d5065694eb9d0b43c312d17a00d2356e36f1
Apply patch set 159029 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 (2815d5065694eb9d0b43c312d17a00d2356e36f1)
Done: main commit 2815d5065694eb9d0b43c312d17a00d2356e36f1
Trying to checkout branch: origin/main
Checked out to main (2815d5065694eb9d0b43c312d17a00d2356e36f1)
Applying patch...
Failed to apply patch:
Applying: pcapng: improve performance of timestamping
error: sha1 information is lacking or useless (lib/pcapng/rte_pcapng.c).
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 pcapng: improve performance of timestamping
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/34679/
UNH-IOL DPDK Community Lab
next prev parent reply other threads:[~2025-11-26 6:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251126051218.50568-1-stephen@networkplumber.org>
2025-11-26 4:42 ` |WARNING| pw159029 " qemudev
2025-11-26 5:12 ` checkpatch
2025-11-26 6:52 ` dpdklab [this message]
2025-11-26 7:52 ` |SUCCESS| " 0-day Robot
2025-11-26 7:52 ` 0-day Robot
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=6926a3a4.050a0220.250248.eb29SMTPIN_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).