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| pw136008 [PATCH] [v2] lib/telemetry:fix telemetry conns le
Date: Sun, 21 Jan 2024 00:30:19 -0800 (PST)	[thread overview]
Message-ID: <65acd61b.050a0220.8425d.8213SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136008

_Testing PASS_

Submitter: Shaowei Sun <1819846787@qq.com>
Date: Saturday, January 20 2024 08:58:32 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:515e1a4f4cddd33fcb35328a73449d30a8edfaf6

136008 --> testing pass

Test environment and result as below:

+-----------------+----------------+
|   Environment   | dpdk_unit_test |
+=================+================+
| CentOS Stream 8 | PASS           |
+-----------------+----------------+


CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28921/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2024-01-21  8:30 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-21  8:30 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-22 21:34 dpdklab
2024-01-22 21:27 dpdklab
2024-01-21 11:16 dpdklab
2024-01-21 11:03 dpdklab
2024-01-21 10:42 dpdklab
2024-01-21 10:37 dpdklab
2024-01-21  9:35 dpdklab
2024-01-21  9:23 dpdklab
2024-01-21  9:16 dpdklab
2024-01-21  9:14 dpdklab
2024-01-21  9:14 dpdklab
2024-01-21  9:11 dpdklab
2024-01-21  9:11 dpdklab
2024-01-21  9:06 dpdklab
2024-01-21  9:03 dpdklab
2024-01-21  9:01 dpdklab
2024-01-21  8:56 dpdklab
2024-01-21  8:56 dpdklab
2024-01-21  8:53 dpdklab
2024-01-21  8:52 dpdklab
2024-01-21  8:51 dpdklab
2024-01-21  8:51 dpdklab
2024-01-21  8:48 dpdklab
2024-01-21  8:45 dpdklab
2024-01-21  8:43 dpdklab
2024-01-21  8:43 dpdklab
2024-01-21  8:42 dpdklab
2024-01-21  8:40 dpdklab
2024-01-21  8:39 dpdklab
2024-01-21  8:38 dpdklab
2024-01-21  8:37 dpdklab
2024-01-21  8:36 dpdklab
2024-01-21  8:33 dpdklab
2024-01-21  8:17 dpdklab
2024-01-21  8:11 dpdklab
2024-01-21  8:10 dpdklab
2024-01-21  8:08 dpdklab
2024-01-21  8:08 dpdklab
2024-01-21  8:07 dpdklab
2024-01-21  8:06 dpdklab
2024-01-21  8:06 dpdklab
2024-01-21  8:04 dpdklab
2024-01-21  8:04 dpdklab
2024-01-21  8:02 dpdklab
2024-01-21  8:02 dpdklab
2024-01-21  8:00 dpdklab
2024-01-21  7:59 dpdklab
2024-01-21  7:57 dpdklab
2024-01-21  7:57 dpdklab
2024-01-21  7:56 dpdklab
2024-01-21  7:56 dpdklab
2024-01-21  7:54 dpdklab
2024-01-21  7:45 dpdklab
2024-01-21  7:45 dpdklab
2024-01-21  7:26 dpdklab
2024-01-21  7:24 dpdklab
2024-01-21  7:21 dpdklab
2024-01-21  7:14 dpdklab
2024-01-21  7:12 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=65acd61b.050a0220.8425d.8213SMTPIN_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).