From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141463 [PATCH] telemetry: fix potential connection issue
Date: Fri, 21 Jun 2024 07:27:25 -0700 (PDT) [thread overview]
Message-ID: <66758dcd.050a0220.a2c18.5701SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240621024037.3412372-1-zhichaox.zeng@intel.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/141463
_Testing PASS_
Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Friday, June 21 2024 02:40:37
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4a44d97f0a52a76258c6a6cb6a713f4380a8ab1f
141463 --> testing pass
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| CentOS Stream 8 | PASS |
+------------------+----------------+
| Debian 12 | PASS |
+------------------+----------------+
| Fedora 37 | PASS |
+------------------+----------------+
| Debian Bullseye | PASS |
+------------------+----------------+
| CentOS Stream 9 | PASS |
+------------------+----------------+
| Fedora 38 | PASS |
+------------------+----------------+
| Fedora 39 | PASS |
+------------------+----------------+
| Fedora 40 | PASS |
+------------------+----------------+
| RHEL8 | PASS |
+------------------+----------------+
| Ubuntu 24.04 | PASS |
+------------------+----------------+
| RHEL9 | PASS |
+------------------+----------------+
| Ubuntu 20.04 | PASS |
+------------------+----------------+
| Ubuntu 22.04 | PASS |
+------------------+----------------+
| openSUSE Leap 15 | PASS |
+------------------+----------------+
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.1.1
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
Ubuntu 24.04
Kernel: 5.4.0-167-generic
Compiler: gcc 13.2.0
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.4.1
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30268/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-06-21 14:27 UTC|newest]
Thread overview: 108+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240621024037.3412372-1-zhichaox.zeng@intel.com>
2024-06-21 2:02 ` qemudev
2024-06-21 2:07 ` qemudev
2024-06-21 2:31 ` checkpatch
2024-06-21 3:25 ` 0-day Robot
2024-06-21 8:06 ` dpdklab
2024-06-21 8:11 ` dpdklab
2024-06-21 8:15 ` dpdklab
2024-06-21 8:16 ` dpdklab
2024-06-21 8:24 ` dpdklab
2024-06-21 8:29 ` dpdklab
2024-06-21 8:35 ` dpdklab
2024-06-21 8:38 ` dpdklab
2024-06-21 8:39 ` dpdklab
2024-06-21 8:43 ` dpdklab
2024-06-21 8:44 ` dpdklab
2024-06-21 8:57 ` dpdklab
2024-06-21 8:58 ` dpdklab
2024-06-21 9:02 ` dpdklab
2024-06-21 9:04 ` dpdklab
2024-06-21 9:05 ` dpdklab
2024-06-21 9:26 ` dpdklab
2024-06-21 13:07 ` dpdklab
2024-06-21 13:12 ` dpdklab
2024-06-21 13:12 ` dpdklab
2024-06-21 13:14 ` dpdklab
2024-06-21 13:14 ` dpdklab
2024-06-21 13:15 ` dpdklab
2024-06-21 13:15 ` dpdklab
2024-06-21 13:16 ` dpdklab
2024-06-21 13:16 ` dpdklab
2024-06-21 13:16 ` dpdklab
2024-06-21 13:18 ` dpdklab
2024-06-21 13:23 ` dpdklab
2024-06-21 13:29 ` dpdklab
2024-06-21 13:30 ` dpdklab
2024-06-21 13:34 ` dpdklab
2024-06-21 13:34 ` dpdklab
2024-06-21 13:41 ` dpdklab
2024-06-21 13:42 ` dpdklab
2024-06-21 13:42 ` dpdklab
2024-06-21 13:45 ` dpdklab
2024-06-21 13:47 ` dpdklab
2024-06-21 13:47 ` dpdklab
2024-06-21 13:49 ` dpdklab
2024-06-21 13:53 ` dpdklab
2024-06-21 14:02 ` dpdklab
2024-06-21 14:04 ` dpdklab
2024-06-21 14:06 ` dpdklab
2024-06-21 14:10 ` dpdklab
2024-06-21 14:11 ` dpdklab
2024-06-21 14:15 ` dpdklab
2024-06-21 14:16 ` dpdklab
2024-06-21 14:16 ` dpdklab
2024-06-21 14:18 ` dpdklab
2024-06-21 14:20 ` dpdklab
2024-06-21 14:22 ` dpdklab
2024-06-21 14:27 ` dpdklab [this message]
2024-06-21 14:28 ` dpdklab
2024-06-21 14:32 ` dpdklab
2024-06-21 14:33 ` dpdklab
2024-06-21 14:35 ` dpdklab
2024-06-21 14:37 ` dpdklab
2024-06-21 14:38 ` dpdklab
2024-06-21 14:39 ` dpdklab
2024-06-21 14:41 ` dpdklab
2024-06-21 14:44 ` dpdklab
2024-06-21 14:45 ` dpdklab
2024-06-21 14:45 ` dpdklab
2024-06-21 14:48 ` dpdklab
2024-06-21 14:49 ` dpdklab
2024-06-21 14:50 ` dpdklab
2024-06-21 14:50 ` dpdklab
2024-06-21 14:51 ` dpdklab
2024-06-21 14:55 ` dpdklab
2024-06-21 14:56 ` dpdklab
2024-06-21 14:56 ` dpdklab
2024-06-21 14:58 ` dpdklab
2024-06-21 14:58 ` dpdklab
2024-06-21 14:59 ` dpdklab
2024-06-21 15:00 ` dpdklab
2024-06-21 15:00 ` dpdklab
2024-06-21 15:01 ` dpdklab
2024-06-21 15:01 ` dpdklab
2024-06-21 15:02 ` dpdklab
2024-06-21 15:02 ` dpdklab
2024-06-21 15:03 ` dpdklab
2024-06-21 15:03 ` dpdklab
2024-06-21 15:03 ` dpdklab
2024-06-21 15:05 ` dpdklab
2024-06-21 15:05 ` dpdklab
2024-06-21 15:05 ` dpdklab
2024-06-21 15:06 ` dpdklab
2024-06-21 15:06 ` dpdklab
2024-06-21 15:07 ` dpdklab
2024-06-21 15:07 ` dpdklab
2024-06-21 15:08 ` dpdklab
2024-06-21 15:09 ` dpdklab
2024-06-21 15:10 ` dpdklab
2024-06-21 15:15 ` dpdklab
2024-06-21 15:23 ` dpdklab
2024-06-21 15:24 ` dpdklab
2024-06-21 15:30 ` dpdklab
2024-06-21 15:30 ` dpdklab
2024-06-21 15:36 ` dpdklab
2024-06-21 16:13 ` dpdklab
2024-06-21 20:06 ` dpdklab
2024-06-21 20:19 ` dpdklab
2024-06-22 11:37 ` 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=66758dcd.050a0220.a2c18.5701SMTPIN_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).