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| pw138001 [PATCH] net/mlx5: fix async flow create error han
Date: Wed, 06 Mar 2024 01:00:01 -0800 (PST)	[thread overview]
Message-ID: <65e83091.050a0220.4a659.a3f0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240305180514.50520-1-dsosnowski@nvidia.com>

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

_Testing PASS_

Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Tuesday, March 05 2024 18:05:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3472e5d3295d44b4835ffb22c39f2b7d40780f10

138001 --> testing pass

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE                   | PASS               |
+----------------------------------------+--------------------+
| Fedora 38 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM)               | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM)                     | PASS               |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM)                  | PASS               |
+----------------------------------------+--------------------+
| Fedora 37 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               |
+----------------------------------------+--------------------+
| Debian 12 (arm)                        | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile   | 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

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

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

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

Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: gcc 9.3.0

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 version 10.0.0-4ubuntu1

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

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-06  9:00 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240305180514.50520-1-dsosnowski@nvidia.com>
2024-03-05 17:47 ` |SUCCESS| pw138001 [PATCH] net/mlx5: fix async flow create error handling qemudev
2024-03-05 17:51 ` qemudev
2024-03-05 18:07 ` checkpatch
2024-03-06  7:51 ` |SUCCESS| pw138001 [PATCH] net/mlx5: fix async flow create error han dpdklab
2024-03-06  7:51 ` dpdklab
2024-03-06  7:53 ` dpdklab
2024-03-06  7:55 ` dpdklab
2024-03-06  7:58 ` dpdklab
2024-03-06  8:02 ` dpdklab
2024-03-06  8:09 ` dpdklab
2024-03-06  8:10 ` dpdklab
2024-03-06  8:13 ` dpdklab
2024-03-06  8:15 ` dpdklab
2024-03-06  8:18 ` dpdklab
2024-03-06  8:19 ` dpdklab
2024-03-06  8:27 ` dpdklab
2024-03-06  8:41 ` dpdklab
2024-03-06  8:41 ` dpdklab
2024-03-06  8:42 ` dpdklab
2024-03-06  8:43 ` dpdklab
2024-03-06  8:43 ` dpdklab
2024-03-06  8:43 ` dpdklab
2024-03-06  8:48 ` dpdklab
2024-03-06  8:48 ` dpdklab
2024-03-06  8:52 ` dpdklab
2024-03-06  8:52 ` dpdklab
2024-03-06  8:54 ` dpdklab
2024-03-06  8:56 ` dpdklab
2024-03-06  8:57 ` dpdklab
2024-03-06  8:57 ` dpdklab
2024-03-06  8:57 ` dpdklab
2024-03-06  8:58 ` dpdklab
2024-03-06  8:58 ` dpdklab
2024-03-06  8:59 ` dpdklab
2024-03-06  9:00 ` dpdklab [this message]
2024-03-06  9:00 ` dpdklab
2024-03-06  9:01 ` dpdklab
2024-03-06  9:02 ` dpdklab
2024-03-06  9:02 ` dpdklab
2024-03-06  9:03 ` dpdklab
2024-03-06  9:03 ` dpdklab
2024-03-06  9:03 ` dpdklab
2024-03-06  9:04 ` dpdklab
2024-03-06  9:04 ` dpdklab
2024-03-06  9:05 ` dpdklab
2024-03-06  9:05 ` dpdklab
2024-03-06  9:06 ` dpdklab
2024-03-06  9:07 ` dpdklab
2024-03-06  9:43 ` dpdklab
2024-03-06  9:45 ` dpdklab
2024-03-06  9:45 ` dpdklab
2024-03-06  9:47 ` dpdklab
2024-03-06  9:51 ` dpdklab
2024-03-06  9:55 ` dpdklab
2024-03-06  9:56 ` dpdklab
2024-03-06  9:57 ` dpdklab
2024-03-06  9:58 ` dpdklab
2024-03-06  9:58 ` dpdklab
2024-03-06  9:59 ` dpdklab
2024-03-06 10:02 ` dpdklab
2024-03-06 10:03 ` dpdklab
2024-03-06 10:03 ` dpdklab
2024-03-06 10:05 ` dpdklab
2024-03-06 10:06 ` dpdklab
2024-03-06 10:08 ` dpdklab
2024-03-06 10:11 ` dpdklab
2024-03-06 10:14 ` dpdklab
2024-03-06 10:26 ` dpdklab
2024-03-06 10:29 ` dpdklab
2024-03-06 10:51 ` dpdklab
2024-03-06 11:07 ` dpdklab
2024-03-10 20:06 ` dpdklab
2024-03-10 20:42 ` dpdklab
2024-03-10 21:35 ` 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=65e83091.050a0220.4a659.a3f0SMTPIN_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).