From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134166-134165 [PATCH] [v5,2/2] examples/l3fwd: relax RX
Date: Mon, 13 Nov 2023 13:16:23 -0800 (PST) [thread overview]
Message-ID: <65529227.170a0220.5922f.8aacSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/134165
_Testing PASS_
Submitter: Trevor Tao <taozj888@163.com>
Date: Monday, November 13 2023 16:11:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d677a3eb1b4e2d38c193fabd755dac30ee04c2df
134166-134165 --> testing pass
Test environment and result as below:
+---------------------+--------------------+
| Environment | dpdk_meson_compile |
+=====================+====================+
| FreeBSD 13 | PASS |
+---------------------+--------------------+
| CentOS Stream 8 | PASS |
+---------------------+--------------------+
| CentOS Stream 9 | PASS |
+---------------------+--------------------+
| Debian Bullseye | PASS |
+---------------------+--------------------+
| Fedora 38 | PASS |
+---------------------+--------------------+
| openSUSE Leap 15 | PASS |
+---------------------+--------------------+
| RHEL8 | PASS |
+---------------------+--------------------+
| Windows Server 2019 | PASS |
+---------------------+--------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
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
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28358/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-13 21:16 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 21:16 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-15 22:38 dpdklab
2023-11-15 21:58 dpdklab
2023-11-14 3:06 dpdklab
2023-11-13 23:27 dpdklab
2023-11-13 23:12 dpdklab
2023-11-13 22:52 dpdklab
2023-11-13 22:41 dpdklab
2023-11-13 22:35 dpdklab
2023-11-13 22:34 dpdklab
2023-11-13 22:22 dpdklab
2023-11-13 22:21 dpdklab
2023-11-13 22:19 dpdklab
2023-11-13 22:19 dpdklab
2023-11-13 22:18 dpdklab
2023-11-13 22:09 dpdklab
2023-11-13 22:07 dpdklab
2023-11-13 22:05 dpdklab
2023-11-13 21:57 dpdklab
2023-11-13 21:27 dpdklab
2023-11-13 21:27 dpdklab
2023-11-13 21:27 dpdklab
2023-11-13 21:27 dpdklab
2023-11-13 21:25 dpdklab
2023-11-13 21:25 dpdklab
2023-11-13 21:24 dpdklab
2023-11-13 21:21 dpdklab
2023-11-13 21:20 dpdklab
2023-11-13 21:20 dpdklab
2023-11-13 21:19 dpdklab
2023-11-13 21:19 dpdklab
2023-11-13 21:19 dpdklab
2023-11-13 21:18 dpdklab
2023-11-13 21:17 dpdklab
2023-11-13 21:17 dpdklab
2023-11-13 21:17 dpdklab
2023-11-13 21:15 dpdklab
2023-11-13 21:15 dpdklab
2023-11-13 21:15 dpdklab
2023-11-13 21:14 dpdklab
2023-11-13 21:14 dpdklab
2023-11-13 21:12 dpdklab
2023-11-13 21:12 dpdklab
2023-11-13 21:11 dpdklab
2023-11-13 20:57 dpdklab
2023-11-13 20:57 dpdklab
2023-11-13 20:53 dpdklab
2023-11-13 20:52 dpdklab
2023-11-13 20:47 dpdklab
2023-11-13 20:47 dpdklab
2023-11-13 20:45 dpdklab
2023-11-13 20:44 dpdklab
2023-11-13 20:44 dpdklab
2023-11-13 20:39 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=65529227.170a0220.5922f.8aacSMTPIN_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).