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| pw137200 [PATCH] net/mlx5: link status change for bonding
Date: Mon, 26 Feb 2024 07:50:09 -0800 (PST)	[thread overview]
Message-ID: <65dcb331.170a0220.5e27f.aacaSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Haifei Luo <haifeil@nvidia.com>
Date: Monday, February 26 2024 12:03:41 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:260ed642fc7718d1a3058edef381f7aba06bbf44

137200 --> testing pass

Test environment and result as below:

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

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

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 aarch32 GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: gcc 9.3.0

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-26 15:50 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 15:50 dpdklab [this message]
     [not found] <20240226120341.175710-1-haifeil@nvidia.com>
2024-02-28  2:23 ` dpdklab
2024-02-28  2:26 ` dpdklab
2024-02-28  2:29 ` dpdklab
2024-02-28  2:31 ` dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2024-02-26 23:24 dpdklab
2024-02-26 23:15 dpdklab
2024-02-26 19:53 dpdklab
2024-02-26 19:28 dpdklab
2024-02-26 19:04 dpdklab
2024-02-26 15:43 dpdklab
2024-02-26 15:13 dpdklab
2024-02-26 15:11 dpdklab
2024-02-26 15:06 dpdklab
2024-02-26 15:03 dpdklab
2024-02-26 15:02 dpdklab
2024-02-26 15:01 dpdklab
2024-02-26 15:01 dpdklab
2024-02-26 14:58 dpdklab
2024-02-26 14:58 dpdklab
2024-02-26 14:57 dpdklab
2024-02-26 14:56 dpdklab
2024-02-26 14:54 dpdklab
2024-02-26 14:53 dpdklab
2024-02-26 14:52 dpdklab
2024-02-26 14:51 dpdklab
2024-02-26 14:50 dpdklab
2024-02-26 14:50 dpdklab
2024-02-26 14:46 dpdklab
2024-02-26 14:46 dpdklab
2024-02-26 14:45 dpdklab
2024-02-26 14:44 dpdklab
2024-02-26 14:43 dpdklab
2024-02-26 14:42 dpdklab
2024-02-26 14:42 dpdklab
2024-02-26 14:41 dpdklab
2024-02-26 14:41 dpdklab
2024-02-26 14:41 dpdklab
2024-02-26 14:40 dpdklab
2024-02-26 14:40 dpdklab
2024-02-26 14:39 dpdklab
2024-02-26 14:38 dpdklab
2024-02-26 14:37 dpdklab
2024-02-26 14:37 dpdklab
2024-02-26 14:36 dpdklab
2024-02-26 14:36 dpdklab
2024-02-26 14:35 dpdklab
2024-02-26 14:35 dpdklab
2024-02-26 14:34 dpdklab
2024-02-26 14:34 dpdklab
2024-02-26 14:34 dpdklab
2024-02-26 14:34 dpdklab
2024-02-26 14:33 dpdklab
2024-02-26 14:33 dpdklab
2024-02-26 14:33 dpdklab
2024-02-26 14:33 dpdklab
2024-02-26 14:33 dpdklab
2024-02-26 14:32 dpdklab
2024-02-26 14:32 dpdklab
2024-02-26 14:32 dpdklab
2024-02-26 14:32 dpdklab
2024-02-26 14:32 dpdklab
2024-02-26 14:32 dpdklab
2024-02-26 14:32 dpdklab
2024-02-26 14:30 dpdklab
2024-02-26 14:27 dpdklab
2024-02-26 14:27 dpdklab
2024-02-26 14:26 dpdklab
2024-02-26 14:25 dpdklab
2024-02-26 14:25 dpdklab
2024-02-26 14:12 dpdklab
2024-02-26 14:11 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=65dcb331.170a0220.5e27f.aacaSMTPIN_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).