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] 0f80c13b4d589f63a8ede56bea0a443750bdcc47
Date: Tue, 26 Jul 2022 06:06:20 +0000 (UTC)	[thread overview]
Message-ID: <20220726060620.467E361956@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

_Testing PASS_

Branch: tags/v21.11

0f80c13b4d589f63a8ede56bea0a443750bdcc47 --> testing pass

Test environment and result as below:

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-07-26  6:06 UTC|newest]

Thread overview: 213+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26  6:06 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-08  5:39 dpdklab
2022-08-08  5:35 dpdklab
2022-08-08  5:30 dpdklab
2022-08-08  5:26 dpdklab
2022-08-08  5:15 dpdklab
2022-08-07  5:53 dpdklab
2022-08-07  5:40 dpdklab
2022-08-07  5:35 dpdklab
2022-08-07  5:31 dpdklab
2022-08-07  5:15 dpdklab
2022-08-06  5:44 dpdklab
2022-08-06  5:37 dpdklab
2022-08-06  5:34 dpdklab
2022-08-06  5:31 dpdklab
2022-08-06  5:18 dpdklab
2022-08-05  6:18 dpdklab
2022-08-05  6:15 dpdklab
2022-08-05  6:04 dpdklab
2022-08-05  6:03 dpdklab
2022-08-05  5:48 dpdklab
2022-08-05  5:48 dpdklab
2022-08-05  5:43 dpdklab
2022-08-05  5:36 dpdklab
2022-08-05  5:33 dpdklab
2022-08-05  5:30 dpdklab
2022-08-05  5:29 dpdklab
2022-08-05  5:22 dpdklab
2022-08-05  5:17 dpdklab
2022-08-05  5:14 dpdklab
2022-08-04  5:48 dpdklab
2022-08-04  5:44 dpdklab
2022-08-04  5:43 dpdklab
2022-08-04  5:41 dpdklab
2022-08-04  5:38 dpdklab
2022-08-04  5:32 dpdklab
2022-08-04  5:23 dpdklab
2022-08-04  5:17 dpdklab
2022-08-04  5:13 dpdklab
2022-08-03  5:59 dpdklab
2022-08-03  5:47 dpdklab
2022-08-03  5:45 dpdklab
2022-08-03  5:45 dpdklab
2022-08-03  5:39 dpdklab
2022-08-03  5:38 dpdklab
2022-08-03  5:33 dpdklab
2022-08-03  5:27 dpdklab
2022-08-03  5:17 dpdklab
2022-08-03  5:15 dpdklab
2022-08-02  6:12 dpdklab
2022-08-02  6:00 dpdklab
2022-08-02  5:56 dpdklab
2022-08-02  5:54 dpdklab
2022-08-02  5:52 dpdklab
2022-08-02  5:52 dpdklab
2022-08-02  5:50 dpdklab
2022-08-02  5:41 dpdklab
2022-08-02  5:20 dpdklab
2022-08-02  5:11 dpdklab
2022-08-01  6:13 dpdklab
2022-08-01  6:04 dpdklab
2022-08-01  6:01 dpdklab
2022-08-01  5:55 dpdklab
2022-08-01  5:45 dpdklab
2022-08-01  5:40 dpdklab
2022-08-01  5:33 dpdklab
2022-08-01  5:25 dpdklab
2022-08-01  5:24 dpdklab
2022-08-01  5:23 dpdklab
2022-07-31  5:46 dpdklab
2022-07-31  5:37 dpdklab
2022-07-31  5:35 dpdklab
2022-07-31  5:35 dpdklab
2022-07-31  5:33 dpdklab
2022-07-31  5:32 dpdklab
2022-07-31  5:19 dpdklab
2022-07-30  5:54 dpdklab
2022-07-30  5:50 dpdklab
2022-07-30  5:47 dpdklab
2022-07-30  5:43 dpdklab
2022-07-30  5:39 dpdklab
2022-07-30  5:37 dpdklab
2022-07-30  5:31 dpdklab
2022-07-30  5:25 dpdklab
2022-07-30  5:25 dpdklab
2022-07-30  5:17 dpdklab
2022-07-29  6:10 dpdklab
2022-07-29  6:06 dpdklab
2022-07-29  5:55 dpdklab
2022-07-29  5:43 dpdklab
2022-07-29  5:36 dpdklab
2022-07-29  5:30 dpdklab
2022-07-29  5:19 dpdklab
2022-07-29  5:15 dpdklab
2022-07-29  5:12 dpdklab
2022-07-28  6:35 dpdklab
2022-07-28  6:34 dpdklab
2022-07-28  6:32 dpdklab
2022-07-28  6:24 dpdklab
2022-07-28  6:15 dpdklab
2022-07-28  5:42 dpdklab
2022-07-28  5:35 dpdklab
2022-07-28  5:22 dpdklab
2022-07-28  5:18 dpdklab
2022-07-28  5:15 dpdklab
2022-07-28  5:14 dpdklab
2022-07-27  6:26 dpdklab
2022-07-27  6:11 dpdklab
2022-07-27  6:07 dpdklab
2022-07-27  6:06 dpdklab
2022-07-27  6:06 dpdklab
2022-07-27  5:44 dpdklab
2022-07-27  5:37 dpdklab
2022-07-27  5:32 dpdklab
2022-07-27  5:26 dpdklab
2022-07-27  5:25 dpdklab
2022-07-27  5:19 dpdklab
2022-07-26  7:15 dpdklab
2022-07-26  7:11 dpdklab
2022-07-26  6:50 dpdklab
2022-07-26  6:50 dpdklab
2022-07-26  6:37 dpdklab
2022-07-26  6:31 dpdklab
2022-07-26  6:25 dpdklab
2022-07-26  6:10 dpdklab
2022-07-26  5:34 dpdklab
2022-07-26  5:31 dpdklab
2022-07-25  7:47 dpdklab
2022-07-25  6:43 dpdklab
2022-07-25  6:28 dpdklab
2022-07-25  6:21 dpdklab
2022-07-25  6:18 dpdklab
2022-07-25  6:05 dpdklab
2022-07-25  5:52 dpdklab
2022-07-25  5:51 dpdklab
2022-07-25  5:35 dpdklab
2022-07-25  5:18 dpdklab
2022-07-25  5:05 dpdklab
2022-07-24  6:28 dpdklab
2022-07-24  6:24 dpdklab
2022-07-24  6:06 dpdklab
2022-07-24  6:05 dpdklab
2022-07-24  5:49 dpdklab
2022-07-24  5:46 dpdklab
2022-07-24  5:39 dpdklab
2022-07-24  5:35 dpdklab
2022-07-24  5:31 dpdklab
2022-07-24  5:20 dpdklab
2022-07-24  5:17 dpdklab
2022-07-23  6:27 dpdklab
2022-07-23  6:08 dpdklab
2022-07-23  6:06 dpdklab
2022-07-23  5:53 dpdklab
2022-07-23  5:44 dpdklab
2022-07-23  5:42 dpdklab
2022-07-23  5:36 dpdklab
2022-07-23  5:30 dpdklab
2022-07-23  5:19 dpdklab
2022-07-23  5:12 dpdklab
2022-07-23  5:12 dpdklab
2022-07-22  7:05 dpdklab
2022-07-22  6:28 dpdklab
2022-07-22  6:08 dpdklab
2022-07-22  6:01 dpdklab
2022-07-22  5:47 dpdklab
2022-07-22  5:41 dpdklab
2022-07-22  5:41 dpdklab
2022-07-22  5:29 dpdklab
2022-07-22  5:29 dpdklab
2022-07-22  5:22 dpdklab
2022-07-22  5:22 dpdklab
2022-07-21  6:42 dpdklab
2022-07-21  6:40 dpdklab
2022-07-21  6:36 dpdklab
2022-07-21  6:28 dpdklab
2022-07-21  6:18 dpdklab
2022-07-21  5:45 dpdklab
2022-07-21  5:37 dpdklab
2022-07-21  5:25 dpdklab
2022-07-21  5:25 dpdklab
2022-07-21  5:16 dpdklab
2022-07-21  5:11 dpdklab
2022-07-20  7:26 dpdklab
2022-07-20  6:47 dpdklab
2022-07-20  6:38 dpdklab
2022-07-20  6:32 dpdklab
2022-07-20  6:25 dpdklab
2022-07-20  5:46 dpdklab
2022-07-20  5:39 dpdklab
2022-07-20  5:33 dpdklab
2022-07-20  5:22 dpdklab
2022-07-20  5:19 dpdklab
2022-07-20  5:14 dpdklab
2022-07-19  6:24 dpdklab
2022-07-19  5:59 dpdklab
2022-07-19  5:59 dpdklab
2022-07-19  5:57 dpdklab
2022-07-19  5:45 dpdklab
2022-07-19  5:35 dpdklab
2022-07-19  5:33 dpdklab
2022-07-19  5:20 dpdklab
2022-07-19  5:17 dpdklab
2022-07-19  5:14 dpdklab
2022-07-19  3:59 dpdklab
2022-07-19  3:57 dpdklab
2022-07-19  3:50 dpdklab
2022-07-19  3:38 dpdklab
2022-07-19  3:23 dpdklab
2022-07-19  3:20 dpdklab
2022-07-19  3:19 dpdklab
2022-07-19  3:04 dpdklab
2022-07-19  3:04 dpdklab
2022-07-19  2:59 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=20220726060620.467E361956@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).