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] fe4b05502dd6db1061e8c926418277c33f57199d
Date: Fri, 24 Mar 2023 14:29:13 +0000 (UTC)	[thread overview]
Message-ID: <20230324142913.5980060123@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

_Testing PASS_

Branch: tags/v21.11

fe4b05502dd6db1061e8c926418277c33f57199d --> testing pass

Test environment and result as below:

+------------------+--------------------+
|   Environment    | dpdk_meson_compile |
+==================+====================+
| FreeBSD 13       | PASS               |
+------------------+--------------------+
| CentOS Stream 9  | PASS               |
+------------------+--------------------+
| CentOS Stream 8  | PASS               |
+------------------+--------------------+
| Debian Buster    | PASS               |
+------------------+--------------------+
| Debian Bullseye  | PASS               |
+------------------+--------------------+
| Ubuntu 22.04     | PASS               |
+------------------+--------------------+
| openSUSE Leap 15 | PASS               |
+------------------+--------------------+
| RHEL 7           | PASS               |
+------------------+--------------------+
| RHEL8            | PASS               |
+------------------+--------------------+
| Ubuntu 20.04     | PASS               |
+------------------+--------------------+


FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

Ubuntu 22.04
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1-2

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

RHEL 7
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-03-24 14:29 UTC|newest]

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