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] 125a65cb03f845d1b6d5f7078670aa1a49d62513
Date: Fri, 26 Aug 2022 05:46:22 +0000 (UTC)	[thread overview]
Message-ID: <20220826054622.16153601FD@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

_Testing PASS_

Branch: tags/v21.11

125a65cb03f845d1b6d5f7078670aa1a49d62513 --> testing pass

Test environment and result as below:

+-------------------------------+----------------+--------------+
|          Environment          | dpdk_unit_test | lpm_autotest |
+===============================+================+==============+
| Ubuntu 20.04 ARM GCC Native   | PASS           | SKIPPED      |
+-------------------------------+----------------+--------------+
| Ubuntu 20.04 ARM Clang Native | PASS           | SKIPPED      |
+-------------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE          | SKIPPED        | 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 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/21143/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-08-26  5:46 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26  5:46 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-29  6:10 dpdklab
2022-08-29  5:52 dpdklab
2022-08-29  5:40 dpdklab
2022-08-29  5:39 dpdklab
2022-08-29  5:33 dpdklab
2022-08-29  5:32 dpdklab
2022-08-29  5:28 dpdklab
2022-08-29  5:20 dpdklab
2022-08-29  5:13 dpdklab
2022-08-29  5:07 dpdklab
2022-08-28  5:56 dpdklab
2022-08-28  5:40 dpdklab
2022-08-28  5:38 dpdklab
2022-08-28  5:38 dpdklab
2022-08-28  5:34 dpdklab
2022-08-28  5:28 dpdklab
2022-08-28  5:20 dpdklab
2022-08-28  5:10 dpdklab
2022-08-28  5:07 dpdklab
2022-08-27  6:54 dpdklab
2022-08-27  6:04 dpdklab
2022-08-27  5:52 dpdklab
2022-08-27  5:51 dpdklab
2022-08-27  5:41 dpdklab
2022-08-27  5:32 dpdklab
2022-08-27  5:21 dpdklab
2022-08-27  5:17 dpdklab
2022-08-27  5:13 dpdklab
2022-08-27  5:07 dpdklab
2022-08-26  6:10 dpdklab
2022-08-26  6:07 dpdklab
2022-08-26  5:43 dpdklab
2022-08-26  5:33 dpdklab
2022-08-26  5:29 dpdklab
2022-08-26  5:17 dpdklab
2022-08-26  5:11 dpdklab
2022-08-26  5:07 dpdklab
2022-08-26  4:02 dpdklab
2022-08-26  3:38 dpdklab
2022-08-26  3:37 dpdklab
2022-08-26  3:34 dpdklab
2022-08-26  3:32 dpdklab
2022-08-26  3:26 dpdklab
2022-08-26  3:12 dpdklab
2022-08-26  3:12 dpdklab
2022-08-26  3:03 dpdklab
2022-08-26  2:58 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=20220826054622.16153601FD@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).