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, Qi Zhang <qi.z.zhang@intel.com>
Subject: |SUCCESS| [GIT MASTER] a871dfd632b3a3973095beb76ddcfdf61e8e14fb
Date: Wed, 11 Oct 2023 01:24:58 -0700 (PDT)	[thread overview]
Message-ID: <65265bda.0c0a0220.b000f.95b6SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-net-intel

a871dfd632b3a3973095beb76ddcfdf61e8e14fb --> testing pass

Test environment and result as below:

+------------------+----------------+
|   Environment    | dpdk_unit_test |
+==================+================+
| CentOS Stream 9  | PASS           |
+------------------+----------------+
| Debian Buster    | PASS           |
+------------------+----------------+
| Debian Bullseye  | PASS           |
+------------------+----------------+
| Fedora 38        | PASS           |
+------------------+----------------+
| Fedora 37        | PASS           |
+------------------+----------------+
| openSUSE Leap 15 | PASS           |
+------------------+----------------+
| Ubuntu 20.04     | PASS           |
+------------------+----------------+
| Ubuntu 22.04     | PASS           |
+------------------+----------------+
| RHEL8            | PASS           |
+------------------+----------------+
| CentOS Stream 8  | PASS           |
+------------------+----------------+


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

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

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

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

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

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-11  8:24 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11  8:24 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-12 14:41 dpdklab
2023-10-12  7:05 dpdklab
2023-10-12  7:03 dpdklab
2023-10-12  7:02 dpdklab
2023-10-11 14:14 dpdklab
2023-10-11 10:22 dpdklab
2023-10-11  9:47 dpdklab
2023-10-11  9:36 dpdklab
2023-10-11  9:34 dpdklab
2023-10-11  9:16 dpdklab
2023-10-11  9:08 dpdklab
2023-10-11  9:08 dpdklab
2023-10-11  9:07 dpdklab
2023-10-11  9:06 dpdklab
2023-10-11  9:05 dpdklab
2023-10-11  9:03 dpdklab
2023-10-11  8:57 dpdklab
2023-10-11  8:56 dpdklab
2023-10-11  8:56 dpdklab
2023-10-11  8:56 dpdklab
2023-10-11  8:56 dpdklab
2023-10-11  8:55 dpdklab
2023-10-11  8:55 dpdklab
2023-10-11  8:54 dpdklab
2023-10-11  8:53 dpdklab
2023-10-11  8:53 dpdklab
2023-10-11  8:49 dpdklab
2023-10-11  8:40 dpdklab
2023-10-11  8:34 dpdklab
2023-10-11  8:33 dpdklab
2023-10-11  8:29 dpdklab
2023-10-11  8:27 dpdklab
2023-10-11  8:26 dpdklab
2023-10-11  8:23 dpdklab
2023-10-11  8:22 dpdklab
2023-10-11  8:21 dpdklab
2023-10-11  8:19 dpdklab
2023-10-11  8:13 dpdklab
2023-10-11  8:08 dpdklab
2023-10-11  8:05 dpdklab
2023-10-11  2:12 dpdklab
2023-10-11  0:48 dpdklab
2023-10-11  0:43 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=65265bda.0c0a0220.b000f.95b6SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=qi.z.zhang@intel.com \
    --cc=test-report@dpdk.org \
    /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).