From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136870-136869 [PATCH] [v8,2/2] ring: add telemetry cmd f
Date: Mon, 19 Feb 2024 01:15:39 -0800 (PST) [thread overview]
Message-ID: <65d31c3b.170a0220.2cd5b.f2deSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136869
_Testing PASS_
Submitter: Jie Hai <haijie1@huawei.com>
Date: Monday, February 19 2024 08:32:53
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3cb34fb0b0adfeb163b4d0e6d5a232a21bd6f6e0
136870-136869 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29179/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-19 9:15 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 9:15 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-19 14:55 dpdklab
2024-02-19 14:41 dpdklab
2024-02-19 11:12 dpdklab
2024-02-19 11:09 dpdklab
2024-02-19 11:09 dpdklab
2024-02-19 11:08 dpdklab
2024-02-19 10:58 dpdklab
2024-02-19 10:56 dpdklab
2024-02-19 10:56 dpdklab
2024-02-19 10:49 dpdklab
2024-02-19 10:34 dpdklab
2024-02-19 10:34 dpdklab
2024-02-19 10:21 dpdklab
2024-02-19 10:09 dpdklab
2024-02-19 10:09 dpdklab
2024-02-19 10:09 dpdklab
2024-02-19 10:02 dpdklab
2024-02-19 10:02 dpdklab
2024-02-19 9:58 dpdklab
2024-02-19 9:58 dpdklab
2024-02-19 9:56 dpdklab
2024-02-19 9:55 dpdklab
2024-02-19 9:52 dpdklab
2024-02-19 9:52 dpdklab
2024-02-19 9:51 dpdklab
2024-02-19 9:49 dpdklab
2024-02-19 9:47 dpdklab
2024-02-19 9:46 dpdklab
2024-02-19 9:46 dpdklab
2024-02-19 9:45 dpdklab
2024-02-19 9:45 dpdklab
2024-02-19 9:44 dpdklab
2024-02-19 9:41 dpdklab
2024-02-19 9:41 dpdklab
2024-02-19 9:40 dpdklab
2024-02-19 9:39 dpdklab
2024-02-19 9:38 dpdklab
2024-02-19 9:37 dpdklab
2024-02-19 9:37 dpdklab
2024-02-19 9:37 dpdklab
2024-02-19 9:35 dpdklab
2024-02-19 9:34 dpdklab
2024-02-19 9:34 dpdklab
2024-02-19 9:33 dpdklab
2024-02-19 9:31 dpdklab
2024-02-19 9:31 dpdklab
2024-02-19 9:30 dpdklab
2024-02-19 9:27 dpdklab
2024-02-19 9:26 dpdklab
2024-02-19 9:25 dpdklab
2024-02-19 9:23 dpdklab
2024-02-19 9:23 dpdklab
2024-02-19 9:22 dpdklab
2024-02-19 9:21 dpdklab
2024-02-19 9:21 dpdklab
2024-02-19 9:20 dpdklab
2024-02-19 9:20 dpdklab
2024-02-19 9:20 dpdklab
2024-02-19 9:19 dpdklab
2024-02-19 9:18 dpdklab
2024-02-19 9:18 dpdklab
2024-02-19 9:17 dpdklab
2024-02-19 9:17 dpdklab
2024-02-19 9:16 dpdklab
2024-02-19 9:16 dpdklab
2024-02-19 9:16 dpdklab
2024-02-19 9:15 dpdklab
2024-02-19 9:14 dpdklab
2024-02-19 9:13 dpdklab
2024-02-19 9:13 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=65d31c3b.170a0220.2cd5b.f2deSMTPIN_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).