automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw122508-122509 [PATCH] [v2, 3/3] net/cnxk: skip red drop for ingress policer
Date: Wed, 25 Jan 2023 14:42:48 +0000 (UTC)	[thread overview]
Message-ID: <20230125144248.7A5D160962@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 3841 bytes --]

Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/122509

_Testing PASS_

Submitter: Rakesh Kudurumalla <rkudurumalla@marvell.com>
Date: Wednesday, January 25 2023 07:32:31 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2a211079a92e962bbd0ec81e425a6ffc32890e67

122508-122509 --> testing pass

Test environment and result as below:

+-------------------------------+----------------+--------------------+----------------------+
|          Environment          | dpdk_unit_test | dpdk_meson_compile | dpdk_mingw64_compile |
+===============================+================+====================+======================+
| Ubuntu 20.04 ARM GCC Native   | PASS           | SKIPPED            | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+
| Ubuntu 20.04 ARM Clang Native | PASS           | SKIPPED            | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+
| Windows Server 2019           | PASS           | PASS               | PASS                 |
+-------------------------------+----------------+--------------------+----------------------+
| RHEL 7                        | PASS           | SKIPPED            | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+
| RHEL8                         | PASS           | SKIPPED            | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+
| CentOS Stream 9               | PASS           | SKIPPED            | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+
| Ubuntu 22.04                  | PASS           | SKIPPED            | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+
| Ubuntu 20.04                  | PASS           | SKIPPED            | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+
| Debian Buster                 | PASS           | SKIPPED            | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+
| CentOS Stream 8               | PASS           | SKIPPED            | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+
| FreeBSD 13                    | SKIPPED        | PASS               | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+


Ubuntu 20.04 ARM GCC Native
	Kernel: 5.4.0-53-generic
	Compiler: gcc 9.3

Ubuntu 20.04 ARM Clang Native
	Kernel: 5.4.0-53-generic
	Compiler: clang 10.0.0-4ubuntu1

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

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)

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

Ubuntu 22.04
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.1-2

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25076/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2023-01-25 14:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25 14:42 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-26  2:50 dpdklab
2023-01-25 17:34 dpdklab
2023-01-25 14:55 dpdklab
2023-01-25 14:55 dpdklab
2023-01-25 14:47 dpdklab
2023-01-25 14:43 dpdklab
2023-01-25 14:42 dpdklab
2023-01-25 14:04 dpdklab
2023-01-25 14:01 dpdklab
2023-01-25 14:00 dpdklab
2023-01-25 13:50 dpdklab
2023-01-25 13:24 dpdklab
2023-01-25 10:53 dpdklab
2023-01-25  8:23 dpdklab
2023-01-25  8:19 dpdklab
2023-01-25  8:16 dpdklab
2023-01-25  8:12 dpdklab
2023-01-25  8:09 dpdklab
2023-01-25  8:07 dpdklab
2023-01-25  8:06 dpdklab
     [not found] <20230125073231.4007078-3-rkudurumalla@marvell.com>
2023-01-25  7:24 ` |SUCCESS| pw122508-122509 [PATCH v2 " qemudev
2023-01-25  7:28 ` 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=20230125144248.7A5D160962@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).