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| pw137508-137509 [PATCH] [2/2] net/mlx5: fix IP-in-IP tunne
Date: Thu, 29 Feb 2024 13:35:37 -0800 (PST)	[thread overview]
Message-ID: <65e0f8a9.d40a0220.4aa99.72aeSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240229160505.630586-3-getelson@nvidia.com>

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

_Testing PASS_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Thursday, February 29 2024 16:05:04 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:387aefe9fab8f1033071659a758ccda61a220ffd

137508-137509 --> testing pass

Test environment and result as below:

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

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

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

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

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

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

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

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

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 21:36 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240229160505.630586-3-getelson@nvidia.com>
2024-02-29 15:43 ` |SUCCESS| pw137508-137509 [PATCH 2/2] net/mlx5: fix IP-in-IP tunnels recognition qemudev
2024-02-29 15:48 ` qemudev
2024-02-29 16:06 ` |SUCCESS| pw137509 " checkpatch
2024-02-29 17:05 ` 0-day Robot
2024-02-29 18:34 ` |SUCCESS| pw137508-137509 [PATCH] [2/2] net/mlx5: fix IP-in-IP tunne dpdklab
2024-02-29 18:56 ` dpdklab
2024-02-29 18:58 ` dpdklab
2024-02-29 18:59 ` dpdklab
2024-02-29 19:03 ` dpdklab
2024-02-29 19:04 ` dpdklab
2024-02-29 19:06 ` dpdklab
2024-02-29 19:07 ` dpdklab
2024-02-29 19:20 ` dpdklab
2024-02-29 19:24 ` dpdklab
2024-02-29 19:24 ` dpdklab
2024-02-29 19:24 ` dpdklab
2024-02-29 19:25 ` dpdklab
2024-02-29 19:35 ` dpdklab
2024-02-29 19:36 ` dpdklab
2024-02-29 20:04 ` dpdklab
2024-02-29 20:36 ` dpdklab
2024-02-29 20:59 ` dpdklab
2024-02-29 21:03 ` dpdklab
2024-02-29 21:03 ` dpdklab
2024-02-29 21:06 ` dpdklab
2024-02-29 21:07 ` dpdklab
2024-02-29 21:08 ` dpdklab
2024-02-29 21:12 ` dpdklab
2024-02-29 21:13 ` dpdklab
2024-02-29 21:14 ` dpdklab
2024-02-29 21:14 ` dpdklab
2024-02-29 21:14 ` dpdklab
2024-02-29 21:15 ` dpdklab
2024-02-29 21:15 ` dpdklab
2024-02-29 21:15 ` dpdklab
2024-02-29 21:16 ` dpdklab
2024-02-29 21:16 ` dpdklab
2024-02-29 21:16 ` dpdklab
2024-02-29 21:17 ` dpdklab
2024-02-29 21:17 ` dpdklab
2024-02-29 21:17 ` dpdklab
2024-02-29 21:17 ` dpdklab
2024-02-29 21:17 ` dpdklab
2024-02-29 21:17 ` dpdklab
2024-02-29 21:18 ` dpdklab
2024-02-29 21:18 ` dpdklab
2024-02-29 21:19 ` dpdklab
2024-02-29 21:22 ` dpdklab
2024-02-29 21:23 ` dpdklab
2024-02-29 21:26 ` dpdklab
2024-02-29 21:26 ` dpdklab
2024-02-29 21:33 ` dpdklab
2024-02-29 21:33 ` dpdklab
2024-02-29 21:33 ` dpdklab
2024-02-29 21:34 ` dpdklab
2024-02-29 21:35 ` dpdklab [this message]
2024-02-29 21:35 ` dpdklab
2024-02-29 21:37 ` dpdklab
2024-02-29 21:38 ` dpdklab
2024-02-29 21:41 ` dpdklab
2024-02-29 21:46 ` dpdklab
2024-02-29 21:47 ` dpdklab
2024-02-29 21:50 ` dpdklab
2024-02-29 21:51 ` dpdklab
2024-02-29 22:13 ` dpdklab
2024-02-29 22:18 ` dpdklab
2024-02-29 23:58 ` dpdklab
2024-03-01  5:08 ` dpdklab
2024-03-01  9:14 ` dpdklab
2024-03-01  9:20 ` dpdklab
2024-03-01  9:25 ` dpdklab
2024-03-01  9:30 ` dpdklab
2024-03-02  9:28 ` dpdklab
2024-03-03 12:52 ` dpdklab
2024-03-03 13:25 ` dpdklab
2024-03-03 13:57 ` 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=65e0f8a9.d40a0220.4aa99.72aeSMTPIN_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).