automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] d5f1d8130b60f03b74f9b3a366cc8416594ac90e
Date: Sun, 11 Dec 2022 07:33:43 +0000 (UTC)	[thread overview]
Message-ID: <20221211073343.EC75B6052E@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]

_Testing PASS_

Branch: tags/v21.11

d5f1d8130b60f03b74f9b3a366cc8416594ac90e --> testing pass

Test environment and result as below:

+------------------------------------+--------------------+
|            Environment             | dpdk_meson_compile |
+====================================+====================+
| Ubuntu 20.04 ARM GCC Native        | PASS               |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Native      | PASS               |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS               |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE               | PASS               |
+------------------------------------+--------------------+


Ubuntu 20.04 ARM GCC Native
	Kernel: 5.4.0-53-generic
	Compiler: gcc 9.3

Ubuntu 20.04 ARM Clang Native
	Kernel: 5.4.0-53-generic
	Compiler: clang 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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-12-11  7:33 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-11  7:33 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-12  7:59 dpdklab
2022-12-12  7:08 dpdklab
2022-12-12  6:58 dpdklab
2022-12-12  6:58 dpdklab
2022-12-12  6:56 dpdklab
2022-12-12  6:55 dpdklab
2022-12-12  6:49 dpdklab
2022-12-12  6:49 dpdklab
2022-12-12  6:48 dpdklab
2022-12-12  6:47 dpdklab
2022-12-12  6:39 dpdklab
2022-12-12  6:20 dpdklab
2022-12-12  6:16 dpdklab
2022-12-12  6:08 dpdklab
2022-12-12  6:01 dpdklab
2022-12-12  5:59 dpdklab
2022-12-12  5:55 dpdklab
2022-12-11  7:06 dpdklab
2022-12-11  7:06 dpdklab
2022-12-11  6:54 dpdklab
2022-12-11  6:54 dpdklab
2022-12-11  6:52 dpdklab
2022-12-11  6:51 dpdklab
2022-12-11  6:51 dpdklab
2022-12-11  6:50 dpdklab
2022-12-11  6:50 dpdklab
2022-12-11  6:20 dpdklab
2022-12-11  6:16 dpdklab
2022-12-11  6:08 dpdklab
2022-12-11  6:02 dpdklab
2022-12-11  6:00 dpdklab
2022-12-11  5:55 dpdklab
2022-12-10  7:31 dpdklab
2022-12-10  7:08 dpdklab
2022-12-10  7:08 dpdklab
2022-12-10  7:06 dpdklab
2022-12-10  7:05 dpdklab
2022-12-10  7:04 dpdklab
2022-12-10  7:03 dpdklab
2022-12-10  7:00 dpdklab
2022-12-10  6:59 dpdklab
2022-12-10  6:55 dpdklab
2022-12-10  6:50 dpdklab
2022-12-10  6:45 dpdklab
2022-12-10  6:42 dpdklab
2022-12-10  6:34 dpdklab
2022-12-10  6:19 dpdklab
2022-12-10  6:16 dpdklab
2022-12-10  6:07 dpdklab
2022-12-10  6:03 dpdklab
2022-12-10  6:00 dpdklab
2022-12-10  5:54 dpdklab
2022-12-10  5:04 dpdklab
2022-12-10  4:49 dpdklab
2022-12-10  4:33 dpdklab
2022-12-10  4:33 dpdklab
2022-12-10  4:32 dpdklab
2022-12-10  4:31 dpdklab
2022-12-10  4:31 dpdklab
2022-12-10  4:30 dpdklab
2022-12-10  4:30 dpdklab
2022-12-10  4:30 dpdklab
2022-12-10  4:30 dpdklab
2022-12-10  4:20 dpdklab
2022-12-10  4:16 dpdklab
2022-12-10  4:15 dpdklab
2022-12-10  4:04 dpdklab
2022-12-10  4:01 dpdklab
2022-12-10  4:00 dpdklab
2022-12-10  3:55 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=20221211073343.EC75B6052E@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=ktraynor@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).