From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135979 [PATCH] lib/telemetry:fix telemetry conns leak in
Date: Fri, 19 Jan 2024 09:21:44 -0800 (PST) [thread overview]
Message-ID: <65aaafa8.050a0220.c9f04.f36cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/135979
_Functional Testing PASS_
Submitter: Shaowei Sun <1819846787@qq.com>
Date: Friday, January 19 2024 11:40:00
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:775ff373216c56acfeffe862c20af2f216c049ea
135979 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28908/
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-19 17:21 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 17:21 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-22 15:37 dpdklab
2024-01-22 15:30 dpdklab
2024-01-20 8:39 dpdklab
2024-01-19 20:14 dpdklab
2024-01-19 20:05 dpdklab
2024-01-19 20:04 dpdklab
2024-01-19 19:32 dpdklab
2024-01-19 19:31 dpdklab
2024-01-19 19:30 dpdklab
2024-01-19 19:29 dpdklab
2024-01-19 19:28 dpdklab
2024-01-19 19:27 dpdklab
2024-01-19 19:26 dpdklab
2024-01-19 19:26 dpdklab
2024-01-19 19:25 dpdklab
2024-01-19 19:25 dpdklab
2024-01-19 19:23 dpdklab
2024-01-19 19:23 dpdklab
2024-01-19 19:21 dpdklab
2024-01-19 19:19 dpdklab
2024-01-19 19:19 dpdklab
2024-01-19 19:18 dpdklab
2024-01-19 19:17 dpdklab
2024-01-19 19:17 dpdklab
2024-01-19 19:17 dpdklab
2024-01-19 19:16 dpdklab
2024-01-19 19:14 dpdklab
2024-01-19 19:00 dpdklab
2024-01-19 18:57 dpdklab
2024-01-19 18:57 dpdklab
2024-01-19 18:52 dpdklab
2024-01-19 18:51 dpdklab
2024-01-19 18:50 dpdklab
2024-01-19 18:47 dpdklab
2024-01-19 18:45 dpdklab
2024-01-19 18:44 dpdklab
2024-01-19 18:43 dpdklab
2024-01-19 18:43 dpdklab
2024-01-19 18:41 dpdklab
2024-01-19 18:37 dpdklab
2024-01-19 18:36 dpdklab
2024-01-19 18:36 dpdklab
2024-01-19 18:33 dpdklab
2024-01-19 18:33 dpdklab
2024-01-19 18:32 dpdklab
2024-01-19 18:26 dpdklab
2024-01-19 18:26 dpdklab
2024-01-19 18:18 dpdklab
2024-01-19 18:18 dpdklab
2024-01-19 18:17 dpdklab
2024-01-19 18:03 dpdklab
2024-01-19 18:03 dpdklab
2024-01-19 17:51 dpdklab
2024-01-19 17:31 dpdklab
2024-01-19 17:27 dpdklab
2024-01-19 17:19 dpdklab
2024-01-19 16:59 dpdklab
2024-01-19 16:58 dpdklab
2024-01-19 16:48 dpdklab
2024-01-19 16:48 dpdklab
2024-01-19 16:47 dpdklab
2024-01-19 16:44 dpdklab
2024-01-19 16:44 dpdklab
2024-01-19 16:28 dpdklab
2024-01-19 16:26 dpdklab
2024-01-19 16:26 dpdklab
2024-01-19 16:25 dpdklab
2024-01-19 16:23 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=65aaafa8.050a0220.c9f04.f36cSMTPIN_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).