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] 8edef444c7ed4fe0c339e84c641abf8825ad031e
Date: Tue, 02 May 2023 21:54:45 -0700 (PDT)	[thread overview]
Message-ID: <6451e915.170a0220.3a676.4df9SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: tags/v22.11

8edef444c7ed4fe0c339e84c641abf8825ad031e --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| openSUSE Leap 15 | PASS     |
+------------------+----------+
| RHEL 7           | PASS     |
+------------------+----------+
| Ubuntu 22.04     | PASS     |
+------------------+----------+
| Debian Bullseye  | PASS     |
+------------------+----------+
| CentOS Stream 9  | PASS     |
+------------------+----------+
| CentOS Stream 8  | PASS     |
+------------------+----------+
| RHEL8            | PASS     |
+------------------+----------+


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)

Ubuntu 22.04
	Kernel: Container Host Kernel
	Compiler: clang 14.0.5-1.fc36

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-05-03  4:54 UTC|newest]

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