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] 3a9c3000f48bcb13ceada55f0062918711234e8d
Date: Wed, 29 Jun 2022 06:09:41 +0000 (UTC)	[thread overview]
Message-ID: <20220629060941.7BB3A60090@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

_Testing PASS_

Branch: tags/v21.11

3a9c3000f48bcb13ceada55f0062918711234e8d --> 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/20568/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-06-29  6:09 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29  6:09 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-03 21:24 dpdklab
2022-07-03 10:01 dpdklab
2022-07-02 22:41 dpdklab
2022-07-02 21:49 dpdklab
2022-07-01  6:58 dpdklab
2022-07-01  6:40 dpdklab
2022-07-01  6:20 dpdklab
2022-07-01  6:16 dpdklab
2022-07-01  5:44 dpdklab
2022-07-01  5:36 dpdklab
2022-07-01  5:32 dpdklab
2022-07-01  5:21 dpdklab
2022-07-01  5:12 dpdklab
2022-06-30  6:31 dpdklab
2022-06-30  6:24 dpdklab
2022-06-30  6:14 dpdklab
2022-06-30  6:04 dpdklab
2022-06-30  5:46 dpdklab
2022-06-30  5:36 dpdklab
2022-06-30  5:34 dpdklab
2022-06-30  5:26 dpdklab
2022-06-30  5:22 dpdklab
2022-06-29  6:16 dpdklab
2022-06-29  6:09 dpdklab
2022-06-29  5:43 dpdklab
2022-06-29  5:35 dpdklab
2022-06-29  5:23 dpdklab
2022-06-29  5:23 dpdklab
2022-06-29  5:10 dpdklab
2022-06-29  4:36 dpdklab
2022-06-29  4:29 dpdklab
2022-06-29  4:25 dpdklab
2022-06-29  3:45 dpdklab
2022-06-29  3:27 dpdklab
2022-06-29  3:21 dpdklab
2022-06-29  3:15 dpdklab
2022-06-29  3:05 dpdklab
2022-06-29  3:05 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=20220629060941.7BB3A60090@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).