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| pw137467 [PATCH] net/mlx5: fix sync meter processing in HW
Date: Thu, 29 Feb 2024 03:35:01 -0800 (PST)	[thread overview]
Message-ID: <65e06be5.d40a0220.1326a.417eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240229105614.593391-1-getelson@nvidia.com>

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

_Testing PASS_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Thursday, February 29 2024 10:56:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:45d2195f9ea6ead7242af856c799c6f084d874bc

137467 --> testing pass

Test environment and result as below:

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


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

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

Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0

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

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

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

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

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-02-29 11:35 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240229105614.593391-1-getelson@nvidia.com>
2024-02-29 10:34 ` |SUCCESS| pw137467 [PATCH] net/mlx5: fix sync meter processing in HWS setup qemudev
2024-02-29 10:38 ` qemudev
2024-02-29 10:57 ` |WARNING| " checkpatch
2024-02-29 11:33 ` |FAILURE| pw137467 [PATCH] net/mlx5: fix sync meter processing in HW dpdklab
2024-02-29 11:34 ` dpdklab
2024-02-29 11:35 ` dpdklab [this message]
2024-02-29 11:36 ` dpdklab
2024-02-29 11:36 ` dpdklab
2024-02-29 11:36 ` dpdklab
2024-02-29 11:36 ` dpdklab
2024-02-29 11:36 ` |SUCCESS| " dpdklab
2024-02-29 11:37 ` dpdklab
2024-02-29 11:37 ` |FAILURE| " dpdklab
2024-02-29 11:37 ` |SUCCESS| " dpdklab
2024-02-29 11:37 ` |FAILURE| " dpdklab
2024-02-29 11:37 ` |SUCCESS| " dpdklab
2024-02-29 11:38 ` dpdklab
2024-02-29 11:39 ` dpdklab
2024-02-29 11:45 ` |FAILURE| " dpdklab
2024-02-29 11:46 ` |SUCCESS| " dpdklab
2024-02-29 11:46 ` |FAILURE| " dpdklab
2024-02-29 11:46 ` |SUCCESS| " dpdklab
2024-02-29 11:47 ` dpdklab
2024-02-29 11:47 ` dpdklab
2024-02-29 11:47 ` |FAILURE| " dpdklab
2024-02-29 11:47 ` |SUCCESS| " dpdklab
2024-02-29 11:47 ` |FAILURE| " dpdklab
2024-02-29 11:48 ` |SUCCESS| " dpdklab
2024-02-29 11:48 ` dpdklab
2024-02-29 11:48 ` |FAILURE| " dpdklab
2024-02-29 11:48 ` |SUCCESS| " dpdklab
2024-02-29 11:48 ` dpdklab
2024-02-29 11:51 ` dpdklab
2024-02-29 11:51 ` dpdklab
2024-02-29 11:52 ` dpdklab
2024-02-29 11:52 ` |FAILURE| " dpdklab
2024-02-29 11:53 ` |SUCCESS| " dpdklab
2024-02-29 11:53 ` dpdklab
2024-02-29 11:53 ` dpdklab
2024-02-29 11:56 ` dpdklab
2024-02-29 11:57 ` dpdklab
2024-02-29 11:57 ` dpdklab
2024-02-29 11:58 ` dpdklab
2024-02-29 11:58 ` dpdklab
2024-02-29 11:58 ` dpdklab
2024-02-29 11:59 ` dpdklab
2024-02-29 11:59 ` dpdklab
2024-02-29 11:59 ` dpdklab
2024-02-29 11:59 ` dpdklab
2024-02-29 11:59 ` dpdklab
2024-02-29 12:03 ` dpdklab
2024-02-29 12:04 ` |FAILURE| " dpdklab
2024-02-29 12:04 ` |SUCCESS| " dpdklab
2024-02-29 12:04 ` dpdklab
2024-02-29 12:04 ` dpdklab
2024-02-29 12:04 ` dpdklab
2024-02-29 12:05 ` dpdklab
2024-02-29 12:05 ` dpdklab
2024-02-29 12:06 ` dpdklab
2024-02-29 12:06 ` dpdklab
2024-02-29 12:10 ` dpdklab
2024-02-29 12:10 ` dpdklab
2024-02-29 12:11 ` dpdklab
2024-02-29 12:11 ` dpdklab
2024-02-29 12:12 ` dpdklab
2024-02-29 12:59 ` dpdklab
2024-02-29 13:35 ` dpdklab
2024-03-01  4:53 ` dpdklab
2024-03-01  5:00 ` dpdklab
2024-03-01  5:16 ` dpdklab
2024-03-01  5:21 ` dpdklab
2024-03-02  4:05 ` dpdklab
2024-03-02 17:17 ` dpdklab
2024-03-02 17:50 ` dpdklab
2024-03-02 18:22 ` 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=65e06be5.d40a0220.1326a.417eSMTPIN_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).