From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Zhichao Zeng <zhichaox.zeng@intel.com>
Subject: |SUCCESS| pw135184-135186 [PATCH] [v2,3/3] net/iavf: add Tx LLDP com
Date: Thu, 14 Dec 2023 06:31:21 -0800 (PST) [thread overview]
Message-ID: <657b11b9.0d0a0220.dcd1b.2d74SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135186
_Testing PASS_
Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Thursday, December 14 2023 06:58:57
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
135184-135186 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
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/28618/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-14 14:31 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 14:31 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-14 19:29 dpdklab
2023-12-14 17:12 dpdklab
2023-12-14 17:08 dpdklab
2023-12-14 16:29 dpdklab
2023-12-14 16:25 dpdklab
2023-12-14 16:25 dpdklab
2023-12-14 16:24 dpdklab
2023-12-14 16:20 dpdklab
2023-12-14 16:19 dpdklab
2023-12-14 16:17 dpdklab
2023-12-14 16:15 dpdklab
2023-12-14 16:12 dpdklab
2023-12-14 16:11 dpdklab
2023-12-14 16:09 dpdklab
2023-12-14 16:07 dpdklab
2023-12-14 16:05 dpdklab
2023-12-14 16:01 dpdklab
2023-12-14 15:45 dpdklab
2023-12-14 15:33 dpdklab
2023-12-14 15:32 dpdklab
2023-12-14 15:30 dpdklab
2023-12-14 15:29 dpdklab
2023-12-14 15:26 dpdklab
2023-12-14 15:01 dpdklab
2023-12-14 14:49 dpdklab
2023-12-14 14:42 dpdklab
2023-12-14 14:42 dpdklab
2023-12-14 14:42 dpdklab
2023-12-14 14:39 dpdklab
2023-12-14 14:38 dpdklab
2023-12-14 14:36 dpdklab
2023-12-14 14:36 dpdklab
2023-12-14 14:35 dpdklab
2023-12-14 14:35 dpdklab
2023-12-14 14:34 dpdklab
2023-12-14 14:33 dpdklab
2023-12-14 14:31 dpdklab
2023-12-14 14:30 dpdklab
2023-12-14 14:24 dpdklab
2023-12-14 14:23 dpdklab
2023-12-14 14:23 dpdklab
2023-12-14 14:23 dpdklab
2023-12-14 14:22 dpdklab
2023-12-14 14:21 dpdklab
2023-12-14 14:20 dpdklab
2023-12-14 14:19 dpdklab
2023-12-14 14:19 dpdklab
2023-12-14 14:19 dpdklab
2023-12-14 14:15 dpdklab
2023-12-14 14:09 dpdklab
2023-12-14 13:54 dpdklab
2023-12-14 13:46 dpdklab
2023-12-14 13:43 dpdklab
2023-12-14 13:11 dpdklab
2023-12-14 13:06 dpdklab
2023-12-14 13:04 dpdklab
2023-12-14 13:04 dpdklab
2023-12-14 12:59 dpdklab
2023-12-14 12:57 dpdklab
2023-12-14 12:57 dpdklab
2023-12-14 12:52 dpdklab
2023-12-14 12:51 dpdklab
2023-12-14 12:50 dpdklab
2023-12-14 12:50 dpdklab
2023-12-14 12:50 dpdklab
2023-12-14 12:48 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=657b11b9.0d0a0220.dcd1b.2d74SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=zhichaox.zeng@intel.com \
/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).