automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Xueming Li <xuemingl@nvidia.com>
Subject: |SUCCESS| pw129340 [PATCH] [v2] net/mlx5: support symmetric RSS hash
Date: Thu, 06 Jul 2023 06:03:33 -0700 (PDT)	[thread overview]
Message-ID: <64a6bba5.250a0220.60fb0.53dcSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Xueming Li <xuemingl@nvidia.com>
Date: Thursday, July 06 2023 11:55:57 
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: master
  CommitID:93906ee021f568766dd01c24ec32a57af7b123b1

129340 --> testing pass

Test environment and result as below:

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


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

Fedora 38
	Kernel: Depends on container host
	Compiler: clang 16.0.3

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)

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

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

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-07-06 13:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06 13:03 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-14  1:01 dpdklab
2023-07-14  1:01 dpdklab
2023-07-13 20:08 dpdklab
2023-07-13 10:39 dpdklab
2023-07-13 10:33 dpdklab
2023-07-13 10:28 dpdklab
2023-07-12 20:47 dpdklab
2023-07-12 20:38 dpdklab
2023-07-12 19:01 dpdklab
2023-07-12 18:53 dpdklab
2023-07-08 19:45 dpdklab
2023-07-08 19:26 dpdklab
2023-07-07  4:27 dpdklab
2023-07-06 21:11 dpdklab
2023-07-06 20:39 dpdklab
2023-07-06 19:52 dpdklab
2023-07-06 13:05 dpdklab
2023-07-06 13:05 dpdklab
2023-07-06 13:03 dpdklab
2023-07-06 13:01 dpdklab
2023-07-06 13:00 dpdklab
2023-07-06 12:58 dpdklab
2023-07-06 12:56 dpdklab
2023-07-06 12:54 dpdklab
2023-07-06 12:53 dpdklab
2023-07-06 12:49 dpdklab
2023-07-06 12:38 dpdklab
2023-07-06 12:38 dpdklab
2023-07-06 12:37 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=64a6bba5.250a0220.60fb0.53dcSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).