automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Itamar Gozlan <igozlan@nvidia.com>
Subject: |SUCCESS| pw138384-138396 [PATCH] [13/13] net/mlx5/hws: fix port ID
Date: Thu, 14 Mar 2024 11:33:30 -0700 (PDT)	[thread overview]
Message-ID: <65f342fa.b00a0220.9e577.36edSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240314114220.203241-13-igozlan@nvidia.com>

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138396

_Testing PASS_

Submitter: Itamar Gozlan <igozlan@nvidia.com>
Date: Thursday, March 14 2024 11:42:20 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:1585a8ddae09ea651ec0bfd462783b71b90534ab

138384-138396 --> testing pass

Test environment and result as below:

+---------------------+--------------------+
|     Environment     | dpdk_meson_compile |
+=====================+====================+
| FreeBSD 13.2        | PASS               |
+---------------------+--------------------+
| Windows Server 2022 | PASS               |
+---------------------+--------------------+
| Fedora 38           | PASS               |
+---------------------+--------------------+
| CentOS Stream 8     | PASS               |
+---------------------+--------------------+
| CentOS Stream 9     | PASS               |
+---------------------+--------------------+
| Fedora 37           | PASS               |
+---------------------+--------------------+
| Ubuntu 20.04        | PASS               |
+---------------------+--------------------+
| Debian 12 (arm)     | PASS               |
+---------------------+--------------------+
| RHEL8               | PASS               |
+---------------------+--------------------+
| Debian Bullseye     | PASS               |
+---------------------+--------------------+


FreeBSD 13.2
	Kernel: 13.2
	Compiler: clang 11.3.0

Windows Server 2022
	Kernel: OS Build 20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.1.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

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

Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 11

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-14 18:33 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240314114220.203241-13-igozlan@nvidia.com>
2024-03-14 11:23 ` |SUCCESS| pw138384-138396 [PATCH 13/13] net/mlx5/hws: fix port ID for root matcher and rule qemudev
2024-03-14 11:28 ` qemudev
2024-03-14 11:45 ` |SUCCESS| pw138396 " checkpatch
2024-03-14 12:43 ` 0-day Robot
2024-03-14 17:57 ` |SUCCESS| pw138384-138396 [PATCH] [13/13] net/mlx5/hws: fix port ID dpdklab
2024-03-14 17:59 ` dpdklab
2024-03-14 17:59 ` dpdklab
2024-03-14 18:00 ` dpdklab
2024-03-14 18:01 ` dpdklab
2024-03-14 18:13 ` dpdklab
2024-03-14 18:14 ` dpdklab
2024-03-14 18:14 ` dpdklab
2024-03-14 18:16 ` dpdklab
2024-03-14 18:17 ` dpdklab
2024-03-14 18:17 ` dpdklab
2024-03-14 18:18 ` dpdklab
2024-03-14 18:18 ` dpdklab
2024-03-14 18:18 ` dpdklab
2024-03-14 18:18 ` dpdklab
2024-03-14 18:20 ` dpdklab
2024-03-14 18:20 ` dpdklab
2024-03-14 18:20 ` dpdklab
2024-03-14 18:20 ` dpdklab
2024-03-14 18:29 ` dpdklab
2024-03-14 18:30 ` dpdklab
2024-03-14 18:32 ` dpdklab
2024-03-14 18:33 ` dpdklab
2024-03-14 18:33 ` dpdklab [this message]
2024-03-14 18:34 ` dpdklab
2024-03-14 18:34 ` dpdklab
2024-03-14 18:34 ` dpdklab
2024-03-14 18:35 ` dpdklab
2024-03-14 18:35 ` dpdklab
2024-03-14 18:35 ` dpdklab
2024-03-14 18:35 ` dpdklab
2024-03-14 18:36 ` dpdklab
2024-03-14 18:36 ` dpdklab
2024-03-14 18:37 ` dpdklab
2024-03-14 18:37 ` dpdklab
2024-03-14 18:37 ` dpdklab
2024-03-14 18:37 ` dpdklab
2024-03-14 18:37 ` dpdklab
2024-03-14 18:37 ` dpdklab
2024-03-14 18:38 ` dpdklab
2024-03-14 18:38 ` dpdklab
2024-03-14 18:38 ` dpdklab
2024-03-14 18:39 ` dpdklab
2024-03-14 18:39 ` dpdklab
2024-03-14 18:39 ` dpdklab
2024-03-14 18:39 ` dpdklab
2024-03-14 18:39 ` dpdklab
2024-03-14 18:39 ` dpdklab
2024-03-14 18:39 ` dpdklab
2024-03-14 18:39 ` dpdklab
2024-03-14 18:40 ` dpdklab
2024-03-14 18:40 ` dpdklab
2024-03-14 18:40 ` dpdklab
2024-03-14 18:40 ` dpdklab
2024-03-14 18:40 ` dpdklab
2024-03-14 18:40 ` dpdklab
2024-03-14 18:41 ` dpdklab
2024-03-14 18:41 ` dpdklab
2024-03-14 18:42 ` dpdklab
2024-03-14 18:43 ` dpdklab
2024-03-14 18:46 ` dpdklab
2024-03-14 18:47 ` dpdklab
2024-03-14 18:47 ` dpdklab
2024-03-14 18:49 ` dpdklab
2024-03-14 18:52 ` dpdklab
2024-03-14 18:57 ` dpdklab
2024-03-14 19:01 ` dpdklab
2024-03-14 19:09 ` dpdklab
2024-03-14 19:13 ` dpdklab
2024-03-14 19:14 ` dpdklab
2024-03-14 19:53 ` dpdklab
2024-03-18 12:44 ` dpdklab
2024-03-18 13:21 ` 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=65f342fa.b00a0220.9e577.36edSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=igozlan@nvidia.com \
    --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).