From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136007 [PATCH] [v2] lib/telemetry:fix telemetry conns le
Date: Sun, 21 Jan 2024 00:15:53 -0800 (PST) [thread overview]
Message-ID: <65acd2b9.170a0220.5d2eb.e3baSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136007
_Testing PASS_
Submitter: Shaowei Sun <1819846787@qq.com>
Date: Saturday, January 20 2024 08:50:54
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:515e1a4f4cddd33fcb35328a73449d30a8edfaf6
136007 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
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)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28920/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-21 8:15 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 8:15 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-22 21:50 dpdklab
2024-01-22 21:42 dpdklab
2024-01-21 12:25 dpdklab
2024-01-21 12:15 dpdklab
2024-01-21 11:51 dpdklab
2024-01-21 11:39 dpdklab
2024-01-21 9:44 dpdklab
2024-01-21 9:43 dpdklab
2024-01-21 9:42 dpdklab
2024-01-21 9:41 dpdklab
2024-01-21 9:40 dpdklab
2024-01-21 9:38 dpdklab
2024-01-21 9:35 dpdklab
2024-01-21 9:35 dpdklab
2024-01-21 9:34 dpdklab
2024-01-21 9:33 dpdklab
2024-01-21 9:32 dpdklab
2024-01-21 9:32 dpdklab
2024-01-21 9:31 dpdklab
2024-01-21 9:30 dpdklab
2024-01-21 9:28 dpdklab
2024-01-21 9:27 dpdklab
2024-01-21 9:26 dpdklab
2024-01-21 9:26 dpdklab
2024-01-21 9:26 dpdklab
2024-01-21 9:25 dpdklab
2024-01-21 9:23 dpdklab
2024-01-21 9:22 dpdklab
2024-01-21 9:22 dpdklab
2024-01-21 9:21 dpdklab
2024-01-21 9:20 dpdklab
2024-01-21 9:20 dpdklab
2024-01-21 9:20 dpdklab
2024-01-21 9:19 dpdklab
2024-01-21 9:18 dpdklab
2024-01-21 9:17 dpdklab
2024-01-21 9:15 dpdklab
2024-01-21 9:13 dpdklab
2024-01-21 9:12 dpdklab
2024-01-21 9:08 dpdklab
2024-01-21 8:54 dpdklab
2024-01-21 8:43 dpdklab
2024-01-21 8:41 dpdklab
2024-01-21 8:39 dpdklab
2024-01-21 8:38 dpdklab
2024-01-21 8:24 dpdklab
2024-01-21 8:23 dpdklab
2024-01-21 8:18 dpdklab
2024-01-21 8:17 dpdklab
2024-01-21 8:16 dpdklab
2024-01-21 8:16 dpdklab
2024-01-21 8:15 dpdklab
2024-01-21 8:15 dpdklab
2024-01-21 8:13 dpdklab
2024-01-21 8:13 dpdklab
2024-01-21 8:13 dpdklab
2024-01-21 8:10 dpdklab
2024-01-21 8:09 dpdklab
2024-01-21 8:09 dpdklab
2024-01-21 8:09 dpdklab
2024-01-21 8:08 dpdklab
2024-01-21 8:07 dpdklab
2024-01-21 8:02 dpdklab
2024-01-21 7:56 dpdklab
2024-01-21 7:44 dpdklab
2024-01-21 7:42 dpdklab
2024-01-21 7:38 dpdklab
2024-01-21 7:25 dpdklab
2024-01-21 7:24 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=65acd2b9.170a0220.5d2eb.e3baSMTPIN_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).