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
Subject: |SUCCESS| [GIT MASTER] 515e1a4f4cddd33fcb35328a73449d30a8edfaf6
Date: Fri, 19 Jan 2024 18:28:41 -0800 (PST)	[thread overview]
Message-ID: <65ab2fd9.810a0220.3c2e1.c056SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk

515e1a4f4cddd33fcb35328a73449d30a8edfaf6 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| FreeBSD 13          | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Bullseye     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Buster       | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS               | PASS                 |
+---------------------+--------------------+----------------------+
| CentOS Stream 8     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 38           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 37           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+


Windows Server 2022
	Kernel: OS Build 20348.2031
	Compiler: MSVC VS-Preview

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

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

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

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-20  2:28 UTC|newest]

Thread overview: 114+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-20  2:28 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-22 23:38 dpdklab
2024-01-22 23:31 dpdklab
2024-01-22 19:00 dpdklab
2024-01-22 18:50 dpdklab
2024-01-22  4:57 dpdklab
2024-01-22  2:50 dpdklab
2024-01-22  2:26 dpdklab
2024-01-22  2:24 dpdklab
2024-01-22  2:23 dpdklab
2024-01-22  2:23 dpdklab
2024-01-22  2:22 dpdklab
2024-01-22  2:22 dpdklab
2024-01-22  2:21 dpdklab
2024-01-22  2:20 dpdklab
2024-01-22  2:20 dpdklab
2024-01-22  2:19 dpdklab
2024-01-22  2:18 dpdklab
2024-01-22  2:16 dpdklab
2024-01-22  2:13 dpdklab
2024-01-22  2:12 dpdklab
2024-01-22  2:12 dpdklab
2024-01-22  2:12 dpdklab
2024-01-22  2:11 dpdklab
2024-01-22  2:11 dpdklab
2024-01-22  2:10 dpdklab
2024-01-22  2:10 dpdklab
2024-01-22  2:09 dpdklab
2024-01-22  2:09 dpdklab
2024-01-22  2:08 dpdklab
2024-01-22  2:07 dpdklab
2024-01-22  2:07 dpdklab
2024-01-22  2:06 dpdklab
2024-01-22  2:06 dpdklab
2024-01-22  2:06 dpdklab
2024-01-22  2:06 dpdklab
2024-01-22  2:06 dpdklab
2024-01-22  2:05 dpdklab
2024-01-22  2:05 dpdklab
2024-01-22  2:05 dpdklab
2024-01-22  2:05 dpdklab
2024-01-22  2:04 dpdklab
2024-01-22  2:04 dpdklab
2024-01-22  2:04 dpdklab
2024-01-22  2:04 dpdklab
2024-01-22  2:03 dpdklab
2024-01-22  2:03 dpdklab
2024-01-22  2:03 dpdklab
2024-01-22  2:02 dpdklab
2024-01-22  2:02 dpdklab
2024-01-22  2:02 dpdklab
2024-01-22  2:02 dpdklab
2024-01-22  2:01 dpdklab
2024-01-22  2:01 dpdklab
2024-01-22  2:00 dpdklab
2024-01-22  2:00 dpdklab
2024-01-22  1:59 dpdklab
2024-01-22  1:58 dpdklab
2024-01-22  1:58 dpdklab
2024-01-20 13:28 dpdklab
2024-01-20  7:12 dpdklab
2024-01-20  6:37 dpdklab
2024-01-20  5:32 dpdklab
2024-01-20  3:20 dpdklab
2024-01-20  3:19 dpdklab
2024-01-20  3:18 dpdklab
2024-01-20  3:16 dpdklab
2024-01-20  3:15 dpdklab
2024-01-20  3:14 dpdklab
2024-01-20  3:14 dpdklab
2024-01-20  3:13 dpdklab
2024-01-20  3:13 dpdklab
2024-01-20  3:13 dpdklab
2024-01-20  3:12 dpdklab
2024-01-20  3:12 dpdklab
2024-01-20  3:10 dpdklab
2024-01-20  3:09 dpdklab
2024-01-20  3:04 dpdklab
2024-01-20  3:02 dpdklab
2024-01-20  3:00 dpdklab
2024-01-20  3:00 dpdklab
2024-01-20  3:00 dpdklab
2024-01-20  2:33 dpdklab
2024-01-20  2:32 dpdklab
2024-01-20  2:32 dpdklab
2024-01-20  2:30 dpdklab
2024-01-20  2:30 dpdklab
2024-01-20  2:29 dpdklab
2024-01-20  2:28 dpdklab
2024-01-20  2:28 dpdklab
2024-01-20  2:27 dpdklab
2024-01-20  2:27 dpdklab
2024-01-20  2:26 dpdklab
2024-01-20  2:26 dpdklab
2024-01-20  2:26 dpdklab
2024-01-20  2:25 dpdklab
2024-01-20  2:25 dpdklab
2024-01-20  2:25 dpdklab
2024-01-20  2:22 dpdklab
2024-01-20  2:22 dpdklab
2024-01-20  2:22 dpdklab
2024-01-20  2:21 dpdklab
2024-01-20  2:21 dpdklab
2024-01-20  2:20 dpdklab
2024-01-20  2:20 dpdklab
2024-01-20  2:20 dpdklab
2024-01-20  2:20 dpdklab
2024-01-20  2:18 dpdklab
2024-01-20  2:12 dpdklab
2024-01-20  2:10 dpdklab
2024-01-20  2:10 dpdklab
2024-01-20  2:02 dpdklab
2024-01-20  2:02 dpdklab
2024-01-20  2:02 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=65ab2fd9.810a0220.3c2e1.c056SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).