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, Akhil Goyal <gakhil@marvell.com>
Subject: |SUCCESS| [GIT MASTER] 4aa3ea9d5a17df941fab13a648e69b8de8573992
Date: Tue, 20 Feb 2024 13:50:13 -0800 (PST)	[thread overview]
Message-ID: <65d51e95.050a0220.87d7b.7275SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-crypto

4aa3ea9d5a17df941fab13a648e69b8de8573992 --> testing pass

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE                   | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile     | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               |
+----------------------------------------+--------------------+
| 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               |
+----------------------------------------+--------------------+


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 GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0

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

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

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28072/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-20 21:50 UTC|newest]

Thread overview: 114+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20 21:50 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-21 14:22 dpdklab
2024-02-21 13:53 dpdklab
2024-02-21 13:34 dpdklab
2024-02-21  7:15 dpdklab
2024-02-21  7:00 dpdklab
2024-02-21  6:31 dpdklab
2024-02-21  5:21 dpdklab
2024-02-20 22:36 dpdklab
2024-02-20 21:57 dpdklab
2024-02-20 21:45 dpdklab
2024-02-20 21:44 dpdklab
2024-02-20 21:42 dpdklab
2024-02-20 21:41 dpdklab
2024-02-20 21:40 dpdklab
2024-02-20 21:39 dpdklab
2024-02-20 21:39 dpdklab
2024-02-20 21:38 dpdklab
2024-02-20 21:37 dpdklab
2024-02-20 21:30 dpdklab
2024-02-20 21:24 dpdklab
2024-02-20 21:24 dpdklab
2024-02-20 21:24 dpdklab
2024-02-20 21:24 dpdklab
2024-02-20 21:23 dpdklab
2024-02-20 21:23 dpdklab
2024-02-20 21:23 dpdklab
2024-02-20 21:23 dpdklab
2024-02-20 21:22 dpdklab
2024-02-20 21:21 dpdklab
2024-02-20 21:20 dpdklab
2024-02-20 21:20 dpdklab
2024-02-20 21:20 dpdklab
2024-02-20 21:20 dpdklab
2024-02-20 21:19 dpdklab
2024-02-20 21:19 dpdklab
2024-02-20 21:19 dpdklab
2024-02-20 21:18 dpdklab
2024-02-20 21:15 dpdklab
2024-02-20 21:11 dpdklab
2024-02-20 21:10 dpdklab
2024-02-20 21:10 dpdklab
2024-02-20 21:10 dpdklab
2024-02-20 21:09 dpdklab
2024-02-20 21:09 dpdklab
2024-02-20 21:08 dpdklab
2024-02-20 21:07 dpdklab
2024-02-20 21:07 dpdklab
2024-02-20 21:07 dpdklab
2024-02-20 21:06 dpdklab
2024-02-20 21:06 dpdklab
2024-02-20 21:06 dpdklab
2024-02-20 21:06 dpdklab
2024-02-20 21:06 dpdklab
2024-02-20 21:05 dpdklab
2024-02-20 20:19 dpdklab
2024-02-20  3:25 dpdklab
2024-02-20  3:19 dpdklab
2024-02-20  3:14 dpdklab
2024-02-20  3:09 dpdklab
2024-02-20  2:55 dpdklab
2024-02-20  2:49 dpdklab
2024-02-20  2:49 dpdklab
2024-02-20  2:47 dpdklab
2024-02-20  2:46 dpdklab
2024-02-20  2:45 dpdklab
2024-02-20  2:44 dpdklab
2024-02-20  2:27 dpdklab
2024-02-20  2:27 dpdklab
2024-02-20  2:04 dpdklab
2024-02-20  2:01 dpdklab
2024-02-20  2:00 dpdklab
2024-02-20  1:59 dpdklab
2024-02-20  1:54 dpdklab
2024-02-20  1:53 dpdklab
2024-02-20  1:52 dpdklab
2024-02-20  1:48 dpdklab
2024-02-20  1:47 dpdklab
2024-02-20  1:47 dpdklab
2024-02-20  1:47 dpdklab
2024-02-20  1:47 dpdklab
2024-02-20  1:45 dpdklab
2024-02-20  1:44 dpdklab
2024-02-20  1:42 dpdklab
2024-02-20  1:42 dpdklab
2024-02-20  1:41 dpdklab
2024-02-20  1:41 dpdklab
2024-02-20  1:40 dpdklab
2024-02-20  1:40 dpdklab
2024-02-20  1:37 dpdklab
2024-02-20  1:36 dpdklab
2024-02-20  1:36 dpdklab
2024-02-20  1:35 dpdklab
2024-02-20  1:34 dpdklab
2024-02-20  1:34 dpdklab
2024-02-20  1:33 dpdklab
2024-02-20  1:33 dpdklab
2024-02-20  1:33 dpdklab
2024-02-20  1:28 dpdklab
2024-02-20  1:25 dpdklab
2024-02-20  1:25 dpdklab
2024-02-20  1:24 dpdklab
2024-02-20  1:24 dpdklab
2024-02-20  1:23 dpdklab
2024-02-20  1:22 dpdklab
2024-02-20  1:22 dpdklab
2024-02-20  1:22 dpdklab
2024-02-20  1:21 dpdklab
2024-02-20  1:21 dpdklab
2024-02-20  1:21 dpdklab
2024-02-20  1:20 dpdklab
2024-02-20  1:20 dpdklab
2024-02-20  1:20 dpdklab
2024-02-20  1: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=65d51e95.050a0220.87d7b.7275SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=gakhil@marvell.com \
    --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).