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
Subject: |SUCCESS| pw135989 [PATCH] lib/telemetry:fix telemetry conns leak in
Date: Fri, 19 Jan 2024 14:54:10 -0800 (PST)	[thread overview]
Message-ID: <65aafd92.050a0220.381dc.046aSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/135989

_Functional 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 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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/

             reply	other threads:[~2024-01-19 22:54 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19 22:54 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:10 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: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=65aafd92.050a0220.381dc.046aSMTPIN_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).