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| pw130033-130037 [PATCH] [5/5] net/mlx5: add support for it
Date: Fri, 11 Aug 2023 15:28:56 -0700 (PDT)	[thread overview]
Message-ID: <64d6b628.170a0220.7ac39.6f36SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Haifei Luo <haifeil@nvidia.com>
Date: Wednesday, August 09 2023 07:40:46 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:70b6941e4e22d67bc10495d1638234a7e974f582

130033-130037 --> testing pass

Test environment and result as below:

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


Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.1.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

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

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

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

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-11 22:28 UTC|newest]

Thread overview: 110+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 22:28 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-14  2:40 dpdklab
2023-08-14  2:26 dpdklab
2023-08-14  2:26 dpdklab
2023-08-14  2:23 dpdklab
2023-08-14  2:23 dpdklab
2023-08-14  2:22 dpdklab
2023-08-14  2:21 dpdklab
2023-08-14  2:20 dpdklab
2023-08-14  2:19 dpdklab
2023-08-14  2:18 dpdklab
2023-08-14  2:18 dpdklab
2023-08-14  2:17 dpdklab
2023-08-13 22:37 dpdklab
2023-08-13 19:20 dpdklab
2023-08-11 23:28 dpdklab
2023-08-11 23:26 dpdklab
2023-08-11 23:11 dpdklab
2023-08-11 22:33 dpdklab
2023-08-11 22:32 dpdklab
2023-08-11 22:31 dpdklab
2023-08-11 22:30 dpdklab
2023-08-11 22:30 dpdklab
2023-08-11 22:28 dpdklab
2023-08-11 22:28 dpdklab
2023-08-11  9:15 dpdklab
2023-08-11  6:49 dpdklab
2023-08-11  6:47 dpdklab
2023-08-11  6:44 dpdklab
2023-08-11  6:42 dpdklab
2023-08-11  6:41 dpdklab
2023-08-11  6:39 dpdklab
2023-08-11  6:38 dpdklab
2023-08-11  6:37 dpdklab
2023-08-11  6:32 dpdklab
2023-08-11  6:28 dpdklab
2023-08-11  6:26 dpdklab
2023-08-11  6:16 dpdklab
2023-08-11  5:43 dpdklab
2023-08-11  5:32 dpdklab
2023-08-11  5:32 dpdklab
2023-08-11  5:30 dpdklab
2023-08-11  5:28 dpdklab
2023-08-11  5:26 dpdklab
2023-08-11  5:25 dpdklab
2023-08-11  5:15 dpdklab
2023-08-11  5:14 dpdklab
2023-08-11  5:04 dpdklab
2023-08-11  4:36 dpdklab
2023-08-11  4:34 dpdklab
2023-08-11  4:33 dpdklab
2023-08-11  4:33 dpdklab
2023-08-11  4:32 dpdklab
2023-08-11  4:32 dpdklab
2023-08-11  4:31 dpdklab
2023-08-11  4:31 dpdklab
2023-08-11  4:30 dpdklab
2023-08-11  4:29 dpdklab
2023-08-11  4:29 dpdklab
2023-08-11  4:29 dpdklab
2023-08-11  4:27 dpdklab
2023-08-11  4:27 dpdklab
2023-08-11  4:27 dpdklab
2023-08-11  4:26 dpdklab
2023-08-11  4:25 dpdklab
2023-08-11  3:53 dpdklab
2023-08-10 23:36 dpdklab
2023-08-10 23:30 dpdklab
2023-08-10 23:15 dpdklab
2023-08-10 22:42 dpdklab
2023-08-10 22:17 dpdklab
2023-08-10 21:43 dpdklab
2023-08-10 20:53 dpdklab
2023-08-10 19:46 dpdklab
2023-08-10 19:19 dpdklab
2023-08-10 19:18 dpdklab
2023-08-10 19:18 dpdklab
2023-08-10 19:15 dpdklab
2023-08-10 19:13 dpdklab
2023-08-10 19:13 dpdklab
2023-08-10 19:13 dpdklab
2023-08-10 19:07 dpdklab
2023-08-10 18:59 dpdklab
2023-08-10 18:44 dpdklab
2023-08-10 18:06 dpdklab
2023-08-10 18:05 dpdklab
2023-08-10 17:58 dpdklab
2023-08-10 17:41 dpdklab
2023-08-10 17:38 dpdklab
2023-08-10 17:38 dpdklab
2023-08-10 17:37 dpdklab
2023-08-10 17:37 dpdklab
2023-08-10 17:36 dpdklab
2023-08-10 17:35 dpdklab
2023-08-10 17:35 dpdklab
2023-08-10 17:34 dpdklab
2023-08-10 17:32 dpdklab
2023-08-10 17:29 dpdklab
2023-08-10 17:22 dpdklab
2023-08-10 17:22 dpdklab
2023-08-10 17:22 dpdklab
2023-08-10 17:22 dpdklab
2023-08-10 17:21 dpdklab
2023-08-10 17:21 dpdklab
2023-08-10 17:20 dpdklab
2023-08-10 17:20 dpdklab
2023-08-10 16:47 dpdklab
2023-08-10 16:47 dpdklab
2023-08-10 16:21 dpdklab
2023-08-10 16:20 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=64d6b628.170a0220.7ac39.6f36SMTPIN_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).