automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@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] 997c669059a4ff49e551deec11b899adba4d73ee
Date: Wed, 01 Nov 2023 18:28:39 -0700 (PDT)	[thread overview]
Message-ID: <6542fb47.250a0220.acf5b.4217SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: 21.11-staging

997c669059a4ff49e551deec11b899adba4d73ee --> testing pass

Test environment and result as below:

+-----------------+----------------+
|   Environment   | dpdk_unit_test |
+=================+================+
| CentOS Stream 8 | PASS           |
+-----------------+----------------+
| Debian Buster   | PASS           |
+-----------------+----------------+
| CentOS Stream 9 | PASS           |
+-----------------+----------------+
| Fedora 38       | PASS           |
+-----------------+----------------+
| Debian Bullseye | PASS           |
+-----------------+----------------+
| Ubuntu 22.04    | PASS           |
+-----------------+----------------+
| Ubuntu 20.04    | PASS           |
+-----------------+----------------+
| RHEL8           | PASS           |
+-----------------+----------------+
| RHEL 7          | PASS           |
+-----------------+----------------+


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

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

Fedora 38
	Kernel: Depends on container host
	Compiler: clang 16.0.3

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

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

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

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)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-02  1:28 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02  1:28 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-02  8:54 dpdklab
2023-11-02  2:22 dpdklab
2023-11-02  2:21 dpdklab
2023-11-02  2:21 dpdklab
2023-11-02  2:16 dpdklab
2023-11-02  2:08 dpdklab
2023-11-02  2:05 dpdklab
2023-11-02  1:49 dpdklab
2023-11-02  1:36 dpdklab
2023-11-02  1:35 dpdklab
2023-11-02  1:33 dpdklab
2023-11-02  1:31 dpdklab
2023-11-02  1:30 dpdklab
2023-11-02  1:29 dpdklab
2023-11-02  1:29 dpdklab
2023-11-02  1:25 dpdklab
2023-11-02  1:23 dpdklab
2023-11-02  1:23 dpdklab
2023-11-02  1:22 dpdklab
2023-11-02  1:21 dpdklab
2023-11-02  1:21 dpdklab
2023-11-02  1:21 dpdklab
2023-11-02  1:20 dpdklab
2023-11-02  1:14 dpdklab
2023-11-02  1:14 dpdklab
2023-11-02  1:13 dpdklab
2023-11-02  1:13 dpdklab
2023-11-02  1:09 dpdklab
2023-11-02  1:09 dpdklab
2023-11-02  1:08 dpdklab
2023-11-02  1:08 dpdklab
2023-11-02  1:02 dpdklab
2023-11-02  1:01 dpdklab
2023-11-02  1:00 dpdklab
2023-11-02  1:00 dpdklab
2023-11-02  0:59 dpdklab
2023-11-02  0:56 dpdklab
2023-11-02  0:48 dpdklab
2023-11-02  0:47 dpdklab
2023-11-02  0:45 dpdklab
2023-11-02  0:43 dpdklab
2023-11-02  0:34 dpdklab
2023-11-02  0:27 dpdklab
2023-11-02  0:27 dpdklab
2023-11-02  0:27 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=6542fb47.250a0220.acf5b.4217SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).