From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130334 [PATCH] [v1,1/3] ethdev: introduce maximum Rx buf
Date: Tue, 15 Aug 2023 07:44:45 -0700 (PDT) [thread overview]
Message-ID: <64db8f5d.020a0220.d7d47.40daSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130334
_Testing PASS_
Submitter: Huisong Li <lihuisong@huawei.com>
Date: Tuesday, August 15 2023 11:10:32
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:68150b90bda5e8f81ad1b1bad82be653b1d42a81
130334 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
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
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27342/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-15 14:44 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 14:44 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-15 16:57 dpdklab
2023-08-15 16:31 dpdklab
2023-08-15 15:56 dpdklab
2023-08-15 15:47 dpdklab
2023-08-15 15:39 dpdklab
2023-08-15 15:35 dpdklab
2023-08-15 15:19 dpdklab
2023-08-15 15:17 dpdklab
2023-08-15 15:15 dpdklab
2023-08-15 15:14 dpdklab
2023-08-15 15:06 dpdklab
2023-08-15 14:59 dpdklab
2023-08-15 14:59 dpdklab
2023-08-15 14:57 dpdklab
2023-08-15 14:56 dpdklab
2023-08-15 14:55 dpdklab
2023-08-15 14:54 dpdklab
2023-08-15 14:52 dpdklab
2023-08-15 14:52 dpdklab
2023-08-15 14:51 dpdklab
2023-08-15 14:50 dpdklab
2023-08-15 14:48 dpdklab
2023-08-15 14:48 dpdklab
2023-08-15 14:46 dpdklab
2023-08-15 14:45 dpdklab
2023-08-15 14:45 dpdklab
2023-08-15 14:44 dpdklab
2023-08-15 14:43 dpdklab
2023-08-15 14:42 dpdklab
2023-08-15 14:41 dpdklab
2023-08-15 14:39 dpdklab
2023-08-15 14:37 dpdklab
2023-08-15 14:37 dpdklab
2023-08-15 14:34 dpdklab
2023-08-15 14:32 dpdklab
2023-08-15 14:32 dpdklab
2023-08-15 14:31 dpdklab
2023-08-15 14:31 dpdklab
2023-08-15 14:27 dpdklab
2023-08-15 14:26 dpdklab
2023-08-15 14:26 dpdklab
2023-08-15 14:26 dpdklab
2023-08-15 14:25 dpdklab
2023-08-15 14:24 dpdklab
2023-08-15 14:23 dpdklab
2023-08-15 14:23 dpdklab
2023-08-15 14:19 dpdklab
2023-08-15 14:19 dpdklab
2023-08-15 14:18 dpdklab
2023-08-15 14:17 dpdklab
2023-08-15 14:16 dpdklab
2023-08-15 14:16 dpdklab
2023-08-15 14:15 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=64db8f5d.020a0220.d7d47.40daSMTPIN_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).