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| pw140306 [PATCH] net/mlx5: remove redundant macro
Date: Fri, 24 May 2024 11:51:30 -0700 (PDT)	[thread overview]
Message-ID: <6650e1b2.050a0220.29200.6930SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240524134254.1496949-1-thomas@monjalon.net>

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

_Testing PASS_

Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Friday, May 24 2024 13:42:54 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:58242360b798ccd45190fc9bc68292f26b7c4385

140306 --> testing pass

Test environment and result as below:

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


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

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

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

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

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

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

32-bit Ubuntu 20.04.4 (ARM)
	Kernel: 5.4.0-155-generic aarch64
	Compiler: gcc 9.4

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

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

Fedora 39 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-05-24 18:51 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240524134254.1496949-1-thomas@monjalon.net>
2024-05-24 13:21 ` qemudev
2024-05-24 13:25 ` qemudev
2024-05-24 13:43 ` checkpatch
2024-05-24 14:44 ` 0-day Robot
2024-05-24 17:17 ` dpdklab
2024-05-24 17:18 ` dpdklab
2024-05-24 17:18 ` dpdklab
2024-05-24 17:18 ` dpdklab
2024-05-24 17:18 ` dpdklab
2024-05-24 17:27 ` dpdklab
2024-05-24 17:42 ` dpdklab
2024-05-24 17:42 ` dpdklab
2024-05-24 17:42 ` dpdklab
2024-05-24 17:43 ` dpdklab
2024-05-24 17:43 ` dpdklab
2024-05-24 17:43 ` dpdklab
2024-05-24 17:44 ` dpdklab
2024-05-24 17:44 ` dpdklab
2024-05-24 17:44 ` dpdklab
2024-05-24 17:45 ` dpdklab
2024-05-24 17:45 ` dpdklab
2024-05-24 17:45 ` dpdklab
2024-05-24 17:45 ` dpdklab
2024-05-24 17:46 ` dpdklab
2024-05-24 17:46 ` dpdklab
2024-05-24 17:47 ` dpdklab
2024-05-24 17:47 ` dpdklab
2024-05-24 17:47 ` dpdklab
2024-05-24 17:47 ` dpdklab
2024-05-24 17:47 ` dpdklab
2024-05-24 17:47 ` dpdklab
2024-05-24 17:48 ` dpdklab
2024-05-24 17:48 ` dpdklab
2024-05-24 17:48 ` dpdklab
2024-05-24 17:48 ` dpdklab
2024-05-24 17:49 ` dpdklab
2024-05-24 17:49 ` dpdklab
2024-05-24 17:49 ` dpdklab
2024-05-24 17:49 ` dpdklab
2024-05-24 17:49 ` dpdklab
2024-05-24 17:49 ` dpdklab
2024-05-24 17:50 ` dpdklab
2024-05-24 17:50 ` dpdklab
2024-05-24 17:50 ` dpdklab
2024-05-24 17:50 ` dpdklab
2024-05-24 17:51 ` dpdklab
2024-05-24 17:51 ` dpdklab
2024-05-24 17:51 ` dpdklab
2024-05-24 17:51 ` dpdklab
2024-05-24 17:51 ` dpdklab
2024-05-24 17:51 ` dpdklab
2024-05-24 17:52 ` dpdklab
2024-05-24 17:53 ` dpdklab
2024-05-24 17:53 ` dpdklab
2024-05-24 17:54 ` dpdklab
2024-05-24 17:56 ` dpdklab
2024-05-24 17:56 ` dpdklab
2024-05-24 17:56 ` dpdklab
2024-05-24 17:57 ` dpdklab
2024-05-24 17:58 ` dpdklab
2024-05-24 17:59 ` dpdklab
2024-05-24 18:00 ` dpdklab
2024-05-24 18:00 ` dpdklab
2024-05-24 18:00 ` dpdklab
2024-05-24 18:01 ` dpdklab
2024-05-24 18:04 ` dpdklab
2024-05-24 18:05 ` dpdklab
2024-05-24 18:10 ` dpdklab
2024-05-24 18:15 ` dpdklab
2024-05-24 18:25 ` dpdklab
2024-05-24 18:30 ` dpdklab
2024-05-24 18:46 ` dpdklab
2024-05-24 18:51 ` dpdklab [this message]
2024-05-24 18:56 ` dpdklab
2024-05-24 18:58 ` 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=6650e1b2.050a0220.29200.6930SMTPIN_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).