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] 2a3b212fafaab648cf8abf771da427c991cd5de8
Date: Mon, 17 Jun 2024 11:55:51 -0700 (PDT)	[thread overview]
Message-ID: <667086b7.050a0220.17755.d617SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk

2a3b212fafaab648cf8abf771da427c991cd5de8 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+-------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+====================+======================+===================+
| FreeBSD 13.3        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2019 | PASS               | PASS                 | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2022 | PASS               | PASS                 | PASS              |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 14.1        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+


FreeBSD 13.3
	Kernel: 13.3-RELEASE-p1
	Compiler: clang 17.0.6

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

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

FreeBSD 14.1
	Kernel: 14.1
	Compiler: clang 18.1.5

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-06-17 18:55 UTC|newest]

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17 18:55 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-17 23:41 dpdklab
2024-06-17 23:34 dpdklab
2024-06-17 23:16 dpdklab
2024-06-17 23:08 dpdklab
2024-06-17 23:07 dpdklab
2024-06-17 22:58 dpdklab
2024-06-17 22:58 dpdklab
2024-06-17 22:55 dpdklab
2024-06-17 22:46 dpdklab
2024-06-17 22:42 dpdklab
2024-06-17 22:36 dpdklab
2024-06-17 22:35 dpdklab
2024-06-17 22:34 dpdklab
2024-06-17 22:25 dpdklab
2024-06-17 22:02 dpdklab
2024-06-17 21:49 dpdklab
2024-06-17 21:48 dpdklab
2024-06-17 21:47 dpdklab
2024-06-17 21:00 dpdklab
2024-06-17 20:48 dpdklab
2024-06-17 20:39 dpdklab
2024-06-17 20:38 dpdklab
2024-06-17 20:33 dpdklab
2024-06-17 20:33 dpdklab
2024-06-17 20:32 dpdklab
2024-06-17 20:10 dpdklab
2024-06-17 20:10 dpdklab
2024-06-17 20:10 dpdklab
2024-06-17 20:10 dpdklab
2024-06-17 20:09 dpdklab
2024-06-17 20:09 dpdklab
2024-06-17 20:08 dpdklab
2024-06-17 20:07 dpdklab
2024-06-17 20:07 dpdklab
2024-06-17 20:07 dpdklab
2024-06-17 20:06 dpdklab
2024-06-17 20:05 dpdklab
2024-06-17 20:05 dpdklab
2024-06-17 20:04 dpdklab
2024-06-17 20:04 dpdklab
2024-06-17 20:04 dpdklab
2024-06-17 20:04 dpdklab
2024-06-17 20:03 dpdklab
2024-06-17 20:02 dpdklab
2024-06-17 20:02 dpdklab
2024-06-17 20:02 dpdklab
2024-06-17 20:01 dpdklab
2024-06-17 20:00 dpdklab
2024-06-17 19:58 dpdklab
2024-06-17 19:49 dpdklab
2024-06-17 19:49 dpdklab
2024-06-17 19:42 dpdklab
2024-06-17 19:41 dpdklab
2024-06-17 19:41 dpdklab
2024-06-17 19:39 dpdklab
2024-06-17 19:38 dpdklab
2024-06-17 19:38 dpdklab
2024-06-17 19:27 dpdklab
2024-06-17 19:26 dpdklab
2024-06-17 19:25 dpdklab
2024-06-17 19:20 dpdklab
2024-06-17 19:18 dpdklab
2024-06-17 19:15 dpdklab
2024-06-17 19:12 dpdklab
2024-06-17 19:11 dpdklab
2024-06-17 19:09 dpdklab
2024-06-17 19:05 dpdklab
2024-06-17 19:05 dpdklab
2024-06-17 19:04 dpdklab
2024-06-17 19:04 dpdklab
2024-06-17 19:03 dpdklab
2024-06-17 19:01 dpdklab
2024-06-17 18:58 dpdklab
2024-06-17 18:58 dpdklab
2024-06-17 18:57 dpdklab
2024-06-17 18:56 dpdklab
2024-06-17 18:56 dpdklab
2024-06-17 18:56 dpdklab
2024-06-17 18:53 dpdklab
2024-06-17 18:53 dpdklab
2024-06-17 18:53 dpdklab
2024-06-17 18:51 dpdklab
2024-06-17 18:50 dpdklab
2024-06-17 18:50 dpdklab
2024-06-17 18:50 dpdklab
2024-06-17 18:49 dpdklab
2024-06-17 18:48 dpdklab
2024-06-17 18:47 dpdklab
2024-06-17 18:47 dpdklab
2024-06-17 18:47 dpdklab
2024-06-17 18:46 dpdklab
2024-06-17 18: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=667086b7.050a0220.17755.d617SMTPIN_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).