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,
	Bruce Richardson <bruce.richardson@intel.com>
Subject: |SUCCESS| pw157261-157263 [PATCH] [v5,3/3] net/ice: add PFC statisti
Date: Fri, 03 Oct 2025 06:47:32 -0700 (PDT)	[thread overview]
Message-ID: <68dfd3f4.050a0220.139ff8.7dc3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251003124037.342760-4-vladimir.medvedkin@intel.com>

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

_Testing PASS_

Submitter: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Date: Friday, October 03 2025 12:40:37 
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: master
  CommitID:e7d8cc7ef4df3552575525697079d3c957cfcdaf

157261-157263 --> testing pass

Upstream job id: Windows-Compile-DPDK-VS#7097

Test environment and result as below:

+---------------------+-------------------+--------------------+
|     Environment     | dpdk_msvc_compile | dpdk_meson_compile |
+=====================+===================+====================+
| Windows Server 2022 | PASS              | SKIPPED            |
+---------------------+-------------------+--------------------+
| FreeBSD 14.2        | SKIPPED           | PASS               |
+---------------------+-------------------+--------------------+
| Ubuntu 20.04        | SKIPPED           | PASS               |
+---------------------+-------------------+--------------------+


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

Ubuntu 20.04
	Kernel: 4.19
	Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-10-03 13:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251003124037.342760-4-vladimir.medvedkin@intel.com>
2025-10-03 12:11 ` |SUCCESS| pw157261-157263 [PATCH v5 3/3] net/ice: add PFC statistics qemudev
2025-10-03 12:16 ` qemudev
2025-10-03 12:41 ` |SUCCESS| pw157263 " checkpatch
2025-10-03 13:13 ` |PENDING| pw157261-157263 [PATCH] [v5,3/3] net/ice: add PFC statisti dpdklab
2025-10-03 13:16 ` dpdklab
2025-10-03 13:17 ` |SUCCESS| " dpdklab
2025-10-03 13:21 ` |PENDING| " dpdklab
2025-10-03 13:22 ` |SUCCESS| " dpdklab
2025-10-03 13:25 ` |PENDING| " dpdklab
2025-10-03 13:35 ` |SUCCESS| " dpdklab
2025-10-03 13:35 ` |FAILURE| pw157263 [PATCH v5 3/3] net/ice: add PFC statistics 0-day Robot
2025-10-03 13:38 ` |SUCCESS| pw157261-157263 [PATCH] [v5,3/3] net/ice: add PFC statisti dpdklab
2025-10-03 13:39 ` dpdklab
2025-10-03 13:47 ` dpdklab [this message]
2025-10-03 13:56 ` dpdklab
2025-10-03 14:05 ` dpdklab
2025-10-03 14:09 ` dpdklab
2025-10-03 14:11 ` dpdklab
2025-10-03 14:15 ` dpdklab
2025-10-03 14:37 ` dpdklab
2025-10-03 14:37 ` 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=68dfd3f4.050a0220.139ff8.7dc3SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bruce.richardson@intel.com \
    --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).