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| pw138660-138661 [PATCH] [2/2] net/mlx5/hws: fix port ID fo
Date: Thu, 21 Mar 2024 14:44:57 -0700 (PDT)	[thread overview]
Message-ID: <65fcaa59.250a0220.2dc1e.1469SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240321142414.1573453-2-kliteyn@nvidia.com>

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138661

_Testing PASS_

Submitter: Yevgeny Kliteynik <kliteyn@nvidia.com>
Date: Thursday, March 21 2024 14:24:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2

138660-138661 --> testing pass

Test environment and result as below:

+--------------------------+----------------+---------------------------+------------------------------+
|       Environment        | dpdk_unit_test | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest |
+==========================+================+===========================+==============================+
| Debian 11 (Buster) (ARM) | PASS           | SKIPPED                   | SKIPPED                      |
+--------------------------+----------------+---------------------------+------------------------------+
| CentOS Stream 9 (ARM)    | PASS           | SKIPPED                   | SKIPPED                      |
+--------------------------+----------------+---------------------------+------------------------------+
| Debian 12 (arm)          | PASS           | PASS                      | PASS                         |
+--------------------------+----------------+---------------------------+------------------------------+
| Fedora 38 (ARM)          | PASS           | SKIPPED                   | SKIPPED                      |
+--------------------------+----------------+---------------------------+------------------------------+
| Fedora 37 (ARM)          | PASS           | SKIPPED                   | SKIPPED                      |
+--------------------------+----------------+---------------------------+------------------------------+
| Ubuntu 20.04 (ARM)       | PASS           | SKIPPED                   | SKIPPED                      |
+--------------------------+----------------+---------------------------+------------------------------+
| Fedora 38 (ARM Clang)    | PASS           | SKIPPED                   | SKIPPED                      |
+--------------------------+----------------+---------------------------+------------------------------+


Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.4.1

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

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

Ubuntu 20.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 9.4.0

Fedora 38 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6

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

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-21 21:45 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240321142414.1573453-2-kliteyn@nvidia.com>
2024-03-21 14:03 ` |SUCCESS| pw138660-138661 [PATCH 2/2] net/mlx5/hws: fix port ID for root table qemudev
2024-03-21 14:07 ` qemudev
2024-03-21 14:25 ` |WARNING| pw138661 " checkpatch
2024-03-21 15:24 ` |SUCCESS| " 0-day Robot
2024-03-21 20:15 ` |SUCCESS| pw138660-138661 [PATCH] [2/2] net/mlx5/hws: fix port ID fo dpdklab
2024-03-21 20:36 ` dpdklab
2024-03-21 20:37 ` dpdklab
2024-03-21 20:37 ` dpdklab
2024-03-21 20:39 ` dpdklab
2024-03-21 20:40 ` dpdklab
2024-03-21 20:40 ` dpdklab
2024-03-21 20:51 ` dpdklab
2024-03-21 20:51 ` dpdklab
2024-03-21 20:53 ` dpdklab
2024-03-21 20:54 ` dpdklab
2024-03-21 20:54 ` dpdklab
2024-03-21 20:55 ` dpdklab
2024-03-21 20:56 ` dpdklab
2024-03-21 20:57 ` dpdklab
2024-03-21 20:57 ` dpdklab
2024-03-21 20:57 ` dpdklab
2024-03-21 21:00 ` dpdklab
2024-03-21 21:00 ` dpdklab
2024-03-21 21:00 ` dpdklab
2024-03-21 21:03 ` dpdklab
2024-03-21 21:05 ` dpdklab
2024-03-21 21:18 ` dpdklab
2024-03-21 21:18 ` dpdklab
2024-03-21 21:19 ` dpdklab
2024-03-21 21:19 ` dpdklab
2024-03-21 21:20 ` dpdklab
2024-03-21 21:20 ` dpdklab
2024-03-21 21:20 ` dpdklab
2024-03-21 21:34 ` dpdklab
2024-03-21 21:39 ` dpdklab
2024-03-21 21:40 ` dpdklab
2024-03-21 21:44 ` dpdklab [this message]
2024-03-21 21:45 ` dpdklab
2024-03-21 21:50 ` dpdklab
2024-03-21 22:05 ` dpdklab
2024-03-21 22:06 ` dpdklab
2024-03-21 22:07 ` dpdklab
2024-03-21 22:07 ` dpdklab
2024-03-21 22:08 ` dpdklab
2024-03-21 22:08 ` dpdklab
2024-03-21 22:08 ` dpdklab
2024-03-21 22:09 ` dpdklab
2024-03-21 22:09 ` dpdklab
2024-03-21 22:10 ` dpdklab
2024-03-21 22:10 ` dpdklab
2024-03-21 22:11 ` dpdklab
2024-03-21 22:12 ` dpdklab
2024-03-21 22:12 ` dpdklab
2024-03-21 22:13 ` dpdklab
2024-03-21 22:13 ` dpdklab
2024-03-21 22:13 ` dpdklab
2024-03-21 22:13 ` dpdklab
2024-03-21 22:13 ` dpdklab
2024-03-21 22:14 ` dpdklab
2024-03-21 22:14 ` dpdklab
2024-03-21 22:15 ` dpdklab
2024-03-21 22:16 ` dpdklab
2024-03-21 22:16 ` dpdklab
2024-03-21 22:16 ` dpdklab
2024-03-21 22:17 ` dpdklab
2024-03-21 22:18 ` dpdklab
2024-03-21 22:19 ` dpdklab
2024-03-21 22:20 ` dpdklab
2024-03-21 22:20 ` dpdklab
2024-03-21 22:20 ` dpdklab
2024-03-21 22:21 ` dpdklab
2024-03-21 22:21 ` dpdklab
2024-03-21 22:21 ` dpdklab
2024-03-21 22:23 ` dpdklab
2024-03-21 22:29 ` dpdklab
2024-03-21 22:36 ` dpdklab
2024-03-21 22:44 ` dpdklab
2024-03-21 22:55 ` dpdklab
2024-03-22  3:25 ` dpdklab
2024-03-23 13:38 ` dpdklab
2024-03-23 14:15 ` 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=65fcaa59.250a0220.2dc1e.1469SMTPIN_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).