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| pw154414-154415 [PATCH] [2/2] latencystats: optimize locki
Date: Thu, 12 Jun 2025 18:37:21 -0700 (PDT)	[thread overview]
Message-ID: <684b80d1.050a0220.234d76.6dadSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250613003547.39239-3-stephen@networkplumber.org>

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

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, June 13 2025 00:34:26 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:dbeb8ae8d09387bd525353f4a5aa6ec152cddffa

154414-154415 --> testing pass

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

Test environment and result as below:

+---------------------+-------------------+-------------------------+--------------------+----------------------+
|     Environment     | dpdk_msvc_compile | dpdk_llvm_clang_compile | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+===================+=========================+====================+======================+
| Windows Server 2022 | PASS              | PASS                    | SKIPPED            | PASS                 |
+---------------------+-------------------+-------------------------+--------------------+----------------------+
| FreeBSD 14.2        | SKIPPED           | SKIPPED                 | PASS               | SKIPPED              |
+---------------------+-------------------+-------------------------+--------------------+----------------------+


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

FreeBSD 14.2
	Kernel: 14.2-RELEASE
	Compiler: clang 18.1.6

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-06-13  1:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250613003547.39239-3-stephen@networkplumber.org>
2025-06-13  0:07 ` |SUCCESS| pw154414-154415 [PATCH 2/2] latencystats: optimize locking on transmit qemudev
2025-06-13  0:12 ` qemudev
2025-06-13  0:35 ` |SUCCESS| pw154415 " checkpatch
2025-06-13  1:10 ` |SUCCESS| pw154414-154415 [PATCH] [2/2] latencystats: optimize locki dpdklab
2025-06-13  1:10 ` dpdklab
2025-06-13  1:13 ` |PENDING| " dpdklab
2025-06-13  1:13 ` dpdklab
2025-06-13  1:14 ` dpdklab
2025-06-13  1:17 ` |SUCCESS| " dpdklab
2025-06-13  1:21 ` |PENDING| " dpdklab
2025-06-13  1:24 ` |SUCCESS| " dpdklab
2025-06-13  1:34 ` dpdklab
2025-06-13  1:34 ` dpdklab
2025-06-13  1:35 ` dpdklab
2025-06-13  1:37 ` dpdklab [this message]
2025-06-13  1:44 ` |SUCCESS| pw154415 [PATCH 2/2] latencystats: optimize locking on transmit 0-day Robot
2025-06-13  1:45 ` |SUCCESS| pw154414-154415 [PATCH] [2/2] latencystats: optimize locki dpdklab
2025-06-13  1:46 ` dpdklab
2025-06-13  2:03 ` dpdklab
2025-06-13  4:58 ` |PENDING| " dpdklab
2025-06-13  6:23 ` |WARNING| " dpdklab
2025-06-13  6:24 ` dpdklab
2025-06-13  8:54 ` |SUCCESS| " dpdklab
2025-06-13 13:20 ` 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=684b80d1.050a0220.234d76.6dadSMTPIN_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).