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,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] 4cf59bbc9edf5419a9f2644a132c9a96c071a4c8
Date: Wed, 14 Feb 2024 00:05:49 -0800 (PST)	[thread overview]
Message-ID: <65cc745d.810a0220.1cbd9.3978SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-net

4cf59bbc9edf5419a9f2644a132c9a96c071a4c8 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Debian Buster       | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+
| openSUSE Leap 15    | PASS           |
+---------------------+----------------+


Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

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

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

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

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-14  8:05 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14  8:05 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-14 16:09 dpdklab
2024-02-14 15:34 dpdklab
2024-02-14 14:24 dpdklab
2024-02-14 13:56 dpdklab
2024-02-14 13:36 dpdklab
2024-02-14 12:05 dpdklab
2024-02-14  9:14 dpdklab
2024-02-14  8:22 dpdklab
2024-02-14  8:22 dpdklab
2024-02-14  8:21 dpdklab
2024-02-14  8:20 dpdklab
2024-02-14  8:19 dpdklab
2024-02-14  8:19 dpdklab
2024-02-14  8:18 dpdklab
2024-02-14  8:12 dpdklab
2024-02-14  8:07 dpdklab
2024-02-14  8:07 dpdklab
2024-02-14  8:07 dpdklab
2024-02-14  8:06 dpdklab
2024-02-14  8:06 dpdklab
2024-02-14  8:05 dpdklab
2024-02-14  8:04 dpdklab
2024-02-14  8:04 dpdklab
2024-02-14  8:03 dpdklab
2024-02-14  8:03 dpdklab
2024-02-14  8:03 dpdklab
2024-02-14  8:02 dpdklab
2024-02-14  8:02 dpdklab
2024-02-14  8:02 dpdklab
2024-02-14  8:02 dpdklab
2024-02-14  8:02 dpdklab
2024-02-14  8:01 dpdklab
2024-02-14  8:01 dpdklab
2024-02-14  8:01 dpdklab
2024-02-14  8:01 dpdklab
2024-02-14  8:00 dpdklab
2024-02-14  8:00 dpdklab
2024-02-14  8:00 dpdklab
2024-02-14  8:00 dpdklab
2024-02-14  7:59 dpdklab
2024-02-14  7:58 dpdklab
2024-02-14  7:57 dpdklab
2024-02-14  7:57 dpdklab
2024-02-14  7:57 dpdklab
2024-02-14  7:57 dpdklab
2024-02-14  7:56 dpdklab
2024-02-14  7:56 dpdklab
2024-02-14  7:55 dpdklab
2024-02-14  7:55 dpdklab
2024-02-14  7:55 dpdklab
2024-02-14  7:48 dpdklab
2024-02-14  7:48 dpdklab
2024-02-14  7:47 dpdklab
2024-02-14  7:46 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=65cc745d.810a0220.1cbd9.3978SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ferruh.yigit@amd.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).