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
Subject: |SUCCESS| pw126952 [PATCH] net/mlx5: fix drop action attribute validation
Date: Wed, 17 May 2023 17:20:11 -0700 (PDT)	[thread overview]
Message-ID: <64656f3b.810a0220.2d79c.0708SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Wednesday, May 17 2023 20:36:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a399d7b5a994e335c446d4b15d7622d71dd8848c

126952 --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| Ubuntu 22.04     | PASS     |
+------------------+----------+
| openSUSE Leap 15 | PASS     |
+------------------+----------+
| RHEL8            | PASS     |
+------------------+----------+
| Debian Bullseye  | PASS     |
+------------------+----------+
| CentOS Stream 9  | PASS     |
+------------------+----------+
| CentOS Stream 8  | PASS     |
+------------------+----------+
| Debian Buster    | PASS     |
+------------------+----------+
| RHEL 7           | PASS     |
+------------------+----------+


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

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)

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

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

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

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/26267/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-05-18  0:20 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18  0:20 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-18  5:19 dpdklab
2023-05-18  5:18 dpdklab
2023-05-18  0:35 dpdklab
2023-05-18  0:28 dpdklab
2023-05-18  0:20 dpdklab
2023-05-18  0:14 dpdklab
2023-05-18  0:11 dpdklab
2023-05-18  0:08 dpdklab
2023-05-18  0:07 dpdklab
2023-05-18  0:02 dpdklab
2023-05-18  0:01 dpdklab
2023-05-18  0:01 dpdklab
2023-05-17 23:59 dpdklab
2023-05-17 23:57 dpdklab
2023-05-17 23:56 dpdklab
2023-05-17 23:53 dpdklab
2023-05-17 23:46 dpdklab
2023-05-17 23:44 dpdklab
2023-05-17 23:41 dpdklab
2023-05-17 23:40 dpdklab
2023-05-17 23:36 dpdklab
2023-05-17 23:32 dpdklab
2023-05-17 23:20 dpdklab
2023-05-17 23:20 dpdklab
2023-05-17 23:07 dpdklab
2023-05-17 23:05 dpdklab
2023-05-17 23:03 dpdklab
2023-05-17 23:02 dpdklab
2023-05-17 22:58 dpdklab
     [not found] <20230517203614.538262-1-dsosnowski@nvidia.com>
2023-05-17 20:25 ` qemudev
2023-05-17 20:29 ` qemudev
2023-05-17 20:38 ` checkpatch
2023-05-17 21:59 ` 0-day Robot

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=64656f3b.810a0220.2d79c.0708SMTPIN_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).