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| pw138481 [PATCH] [v2] net/mlx5: fix sync meter action
Date: Tue, 19 Mar 2024 13:07:57 -0700 (PDT)	[thread overview]
Message-ID: <65f9f09d.050a0220.137da.a960SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240319112455.329350-1-getelson@nvidia.com>

Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138481

_Testing PASS_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Tuesday, March 19 2024 11:24:55 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2

138481 --> testing pass

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE                   | PASS               |
+----------------------------------------+--------------------+
| Fedora 37 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM)                  | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM)                     | PASS               |
+----------------------------------------+--------------------+
| Debian 12 with MUSDK                   | PASS               |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM)               | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               |
+----------------------------------------+--------------------+
| Fedora 38 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Debian 12 (arm)                        | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile   | PASS               |
+----------------------------------------+--------------------+


Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-167-generic
	Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0

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

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

Debian 12 with MUSDK
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

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

Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0

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

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

Ubuntu 20.04 ARM Clang Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: clang 10.0.0-4ubuntu1

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

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-19 20:08 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240319112455.329350-1-getelson@nvidia.com>
2024-03-19 11:15 ` |SUCCESS| pw138481 [PATCH v2] " qemudev
2024-03-19 11:19 ` qemudev
2024-03-19 11:26 ` checkpatch
2024-03-19 12:23 ` 0-day Robot
2024-03-19 18:17 ` |SUCCESS| pw138481 [PATCH] [v2] " dpdklab
2024-03-19 18:17 ` dpdklab
2024-03-19 18:20 ` dpdklab
2024-03-19 18:21 ` dpdklab
2024-03-19 18:22 ` dpdklab
2024-03-19 18:22 ` dpdklab
2024-03-19 18:23 ` dpdklab
2024-03-19 18:24 ` dpdklab
2024-03-19 18:26 ` dpdklab
2024-03-19 18:36 ` dpdklab
2024-03-19 18:55 ` dpdklab
2024-03-19 18:55 ` dpdklab
2024-03-19 18:55 ` dpdklab
2024-03-19 18:56 ` dpdklab
2024-03-19 18:58 ` dpdklab
2024-03-19 18:58 ` dpdklab
2024-03-19 18:59 ` dpdklab
2024-03-19 19:00 ` dpdklab
2024-03-19 19:01 ` dpdklab
2024-03-19 19:02 ` dpdklab
2024-03-19 19:04 ` dpdklab
2024-03-19 19:04 ` dpdklab
2024-03-19 19:57 ` dpdklab
2024-03-19 19:58 ` dpdklab
2024-03-19 19:58 ` dpdklab
2024-03-19 20:00 ` dpdklab
2024-03-19 20:01 ` dpdklab
2024-03-19 20:02 ` dpdklab
2024-03-19 20:02 ` dpdklab
2024-03-19 20:02 ` dpdklab
2024-03-19 20:02 ` dpdklab
2024-03-19 20:03 ` dpdklab
2024-03-19 20:03 ` dpdklab
2024-03-19 20:03 ` dpdklab
2024-03-19 20:03 ` dpdklab
2024-03-19 20:03 ` dpdklab
2024-03-19 20:05 ` dpdklab
2024-03-19 20:05 ` dpdklab
2024-03-19 20:05 ` dpdklab
2024-03-19 20:05 ` dpdklab
2024-03-19 20:05 ` dpdklab
2024-03-19 20:05 ` dpdklab
2024-03-19 20:06 ` dpdklab
2024-03-19 20:06 ` dpdklab
2024-03-19 20:06 ` dpdklab
2024-03-19 20:06 ` dpdklab
2024-03-19 20:06 ` dpdklab
2024-03-19 20:06 ` dpdklab
2024-03-19 20:06 ` dpdklab
2024-03-19 20:07 ` dpdklab
2024-03-19 20:07 ` dpdklab
2024-03-19 20:07 ` dpdklab
2024-03-19 20:07 ` dpdklab
2024-03-19 20:07 ` dpdklab
2024-03-19 20:07 ` dpdklab [this message]
2024-03-19 20:08 ` dpdklab
2024-03-19 20:08 ` dpdklab
2024-03-19 20:09 ` dpdklab
2024-03-19 20:10 ` dpdklab
2024-03-19 20:11 ` dpdklab
2024-03-19 20:13 ` dpdklab
2024-03-19 20:13 ` dpdklab
2024-03-19 20:14 ` dpdklab
2024-03-19 20:14 ` dpdklab
2024-03-19 20:14 ` dpdklab
2024-03-19 20:14 ` dpdklab
2024-03-19 20:15 ` dpdklab
2024-03-19 20:16 ` dpdklab
2024-03-19 20:23 ` dpdklab
2024-03-19 20:35 ` dpdklab
2024-03-19 21:06 ` dpdklab
2024-03-19 21:13 ` dpdklab
2024-03-19 21:20 ` dpdklab
2024-03-19 21:34 ` dpdklab
2024-03-20 14:34 ` |WARNING| " dpdklab
2024-03-21  9:19 ` |SUCCESS| " dpdklab
2024-03-21 10:08 ` 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=65f9f09d.050a0220.137da.a960SMTPIN_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).