From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135989 [PATCH] lib/telemetry:fix telemetry conns leak in
Date: Fri, 19 Jan 2024 17:10:54 -0800 (PST) [thread overview]
Message-ID: <65ab1d9e.050a0220.d8a1.e007SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135989
_Testing PASS_
Submitter: Shaowei Sun <1819846787@qq.com>
Date: Friday, January 19 2024 16:25:31
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:515e1a4f4cddd33fcb35328a73449d30a8edfaf6
135989 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Buster | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28912/
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-20 1:10 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 1:10 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-22 18:21 dpdklab
2024-01-22 18:14 dpdklab
2024-01-20 12:34 dpdklab
2024-01-20 4:52 dpdklab
2024-01-20 4:17 dpdklab
2024-01-20 2:28 dpdklab
2024-01-20 2:27 dpdklab
2024-01-20 2:22 dpdklab
2024-01-20 2:21 dpdklab
2024-01-20 2:19 dpdklab
2024-01-20 2:19 dpdklab
2024-01-20 2:11 dpdklab
2024-01-20 2:11 dpdklab
2024-01-20 2:03 dpdklab
2024-01-20 2:02 dpdklab
2024-01-20 1:53 dpdklab
2024-01-20 1:52 dpdklab
2024-01-20 1:48 dpdklab
2024-01-20 1:38 dpdklab
2024-01-20 1:35 dpdklab
2024-01-20 1:35 dpdklab
2024-01-20 1:34 dpdklab
2024-01-20 1:26 dpdklab
2024-01-20 1:25 dpdklab
2024-01-20 1:22 dpdklab
2024-01-20 1:19 dpdklab
2024-01-20 1:19 dpdklab
2024-01-20 1:15 dpdklab
2024-01-20 1:13 dpdklab
2024-01-20 1:12 dpdklab
2024-01-20 1:09 dpdklab
2024-01-20 0:54 dpdklab
2024-01-20 0:48 dpdklab
2024-01-20 0:47 dpdklab
2024-01-20 0:46 dpdklab
2024-01-20 0:38 dpdklab
2024-01-20 0:31 dpdklab
2024-01-20 0:31 dpdklab
2024-01-20 0:24 dpdklab
2024-01-20 0:23 dpdklab
2024-01-20 0:20 dpdklab
2024-01-20 0:18 dpdklab
2024-01-20 0:16 dpdklab
2024-01-20 0:13 dpdklab
2024-01-20 0:12 dpdklab
2024-01-19 23:53 dpdklab
2024-01-19 23:53 dpdklab
2024-01-19 23:45 dpdklab
2024-01-19 23:43 dpdklab
2024-01-19 23:42 dpdklab
2024-01-19 23:42 dpdklab
2024-01-19 23:42 dpdklab
2024-01-19 23:41 dpdklab
2024-01-19 23:41 dpdklab
2024-01-19 23:39 dpdklab
2024-01-19 23:38 dpdklab
2024-01-19 23:38 dpdklab
2024-01-19 23:38 dpdklab
2024-01-19 23:37 dpdklab
2024-01-19 23:30 dpdklab
2024-01-19 23:18 dpdklab
2024-01-19 23:08 dpdklab
2024-01-19 23:08 dpdklab
2024-01-19 23:07 dpdklab
2024-01-19 23:06 dpdklab
2024-01-19 22:54 dpdklab
2024-01-19 22:52 dpdklab
2024-01-19 22:47 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=65ab1d9e.050a0220.d8a1.e007SMTPIN_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).