From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124084-124083 [PATCH] [v11, 3/3] net/cnxk: skip red drop for ingress policer
Date: Thu, 16 Feb 2023 20:21:25 +0000 (UTC) [thread overview]
Message-ID: <20230216202125.58DF1600AB@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2169 bytes --]
Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/124083
_Testing PASS_
Submitter: Rakesh Kudurumalla <rkudurumalla@marvell.com>
Date: Thursday, February 16 2023 14:51:28
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:01314192b7856d3737eb6d80aa351f60a07631af
124084-124083 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| RHEL 7 | 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
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 11.3.1-2
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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)
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25428/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-16 20:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 20:21 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-24 23:11 dpdklab
2023-02-19 12:11 dpdklab
2023-02-18 1:46 dpdklab
2023-02-16 20:32 dpdklab
2023-02-16 20:32 dpdklab
2023-02-16 20:29 dpdklab
2023-02-16 20:25 dpdklab
2023-02-16 20:07 dpdklab
2023-02-16 20:06 dpdklab
2023-02-16 19:56 dpdklab
2023-02-16 19:53 dpdklab
2023-02-16 19:53 dpdklab
2023-02-16 19:51 dpdklab
2023-02-16 19:40 dpdklab
2023-02-16 19:34 dpdklab
2023-02-16 19:22 dpdklab
2023-02-16 15:46 dpdklab
2023-02-16 15:35 dpdklab
2023-02-16 15:34 dpdklab
2023-02-16 15:31 dpdklab
2023-02-16 15:29 dpdklab
[not found] <20230216145128.1734257-3-rkudurumalla@marvell.com>
2023-02-16 14:42 ` |SUCCESS| pw124084-124083 [PATCH v11 " qemudev
2023-02-16 14:46 ` qemudev
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=20230216202125.58DF1600AB@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).