automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw159542-159547 [PATCH] [v2,6/6] pcapng: improve performan
Date: Fri, 09 Jan 2026 22:10:28 -0800 (PST)	[thread overview]
Message-ID: <6961ed54.170a0220.17fcfe.eacdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251229230223.151874-7-stephen@networkplumber.org>

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/159547

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Monday, December 29 2025 23:01:09 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:cd60dcd503b91956f966a1f6d595b35d256ac00f

159542-159547 --> testing pass

Upstream job id: Windows-Compile-DPDK-Native#33298

Test environment and result as below:

+---------------------+--------------------+-------------------------+
|     Environment     | dpdk_meson_compile | dpdk_llvm_clang_compile |
+=====================+====================+=========================+
| FreeBSD 14.2        | PASS               | SKIPPED                 |
+---------------------+--------------------+-------------------------+
| Windows Server 2025 | SKIPPED            | PASS                    |
+---------------------+--------------------+-------------------------+


FreeBSD 14.2
	Kernel: 14.2-RELEASE
	Compiler: clang 18.1.6

Windows Server 2025
	Kernel: 10.0.26100
	Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34829/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2026-01-10  6:10 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251229230223.151874-7-stephen@networkplumber.org>
2025-12-29 23:01 ` |SUCCESS| pw159547 [PATCH v2 6/6] pcapng: improve performance of timestamping checkpatch
2025-12-29 23:01 ` |SUCCESS| pw159542-159547 " qemudev
2025-12-29 23:07 ` qemudev
2025-12-30  0:31 ` |SUCCESS| pw159547 " 0-day Robot
2025-12-30  0:31 ` 0-day Robot
2026-01-09  2:05 ` |SUCCESS| pw159542-159547 [PATCH] [v2,6/6] pcapng: improve performan dpdklab
2026-01-09  2:28 ` dpdklab
2026-01-09  2:31 ` dpdklab
2026-01-09  2:32 ` dpdklab
2026-01-09  2:45 ` dpdklab
2026-01-09  2:50 ` dpdklab
2026-01-09  2:58 ` dpdklab
2026-01-09  3:08 ` dpdklab
2026-01-09  3:12 ` dpdklab
2026-01-09 10:24 ` |PENDING| " dpdklab
2026-01-09 15:01 ` |SUCCESS| " dpdklab
2026-01-09 15:20 ` dpdklab
2026-01-09 15:57 ` dpdklab
2026-01-09 16:31 ` dpdklab
2026-01-09 16:33 ` dpdklab
2026-01-09 16:38 ` dpdklab
2026-01-09 16:43 ` dpdklab
2026-01-09 17:18 ` dpdklab
2026-01-09 17:19 ` dpdklab
2026-01-09 17:20 ` dpdklab
2026-01-09 17:44 ` dpdklab
2026-01-09 18:41 ` |PENDING| " dpdklab
2026-01-09 18:44 ` |SUCCESS| " dpdklab
2026-01-09 19:10 ` dpdklab
2026-01-10  1:06 ` |PENDING| " dpdklab
2026-01-10  6:10 ` dpdklab [this message]
2026-01-10  6:18 ` |SUCCESS| " dpdklab
2026-01-10  6:36 ` dpdklab
2026-01-10 14:20 ` |PENDING| " dpdklab
2026-01-10 15:18 ` |SUCCESS| " dpdklab
2026-01-10 22:06 ` dpdklab
2026-01-10 22:30 ` dpdklab
2026-01-11  0:17 ` dpdklab

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=6961ed54.170a0220.17fcfe.eacdSMTPIN_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).