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] 9ab7baa5c14b1ba928c09bda4734827d6d367d6b
Date: Tue, 25 Jun 2024 21:27:55 -0700 (PDT)	[thread overview]
Message-ID: <667b98cb.4a0a0220.18c56.7064SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk

9ab7baa5c14b1ba928c09bda4734827d6d367d6b --> testing pass

Test environment and result as below:

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


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

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

FreeBSD 14.1
	Kernel: 14.1
	Compiler: clang 18.1.5

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-06-26  4:27 UTC|newest]

Thread overview: 98+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26  4:27 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-26 10:20 dpdklab
2024-06-26  9:48 dpdklab
2024-06-26  9:27 dpdklab
2024-06-26  9:04 dpdklab
2024-06-26  9:02 dpdklab
2024-06-26  6:43 dpdklab
2024-06-26  5:57 dpdklab
2024-06-26  5:55 dpdklab
2024-06-26  5:54 dpdklab
2024-06-26  5:51 dpdklab
2024-06-26  5:47 dpdklab
2024-06-26  5:46 dpdklab
2024-06-26  5:45 dpdklab
2024-06-26  5:45 dpdklab
2024-06-26  5:44 dpdklab
2024-06-26  5:43 dpdklab
2024-06-26  5:42 dpdklab
2024-06-26  5:42 dpdklab
2024-06-26  5:42 dpdklab
2024-06-26  5:41 dpdklab
2024-06-26  5:41 dpdklab
2024-06-26  5:41 dpdklab
2024-06-26  5:40 dpdklab
2024-06-26  5:40 dpdklab
2024-06-26  5:40 dpdklab
2024-06-26  5:40 dpdklab
2024-06-26  5:40 dpdklab
2024-06-26  5:39 dpdklab
2024-06-26  5:37 dpdklab
2024-06-26  5:36 dpdklab
2024-06-26  5:36 dpdklab
2024-06-26  5:36 dpdklab
2024-06-26  5:36 dpdklab
2024-06-26  5:35 dpdklab
2024-06-26  5:35 dpdklab
2024-06-26  5:35 dpdklab
2024-06-26  5:34 dpdklab
2024-06-26  5:34 dpdklab
2024-06-26  5:34 dpdklab
2024-06-26  5:32 dpdklab
2024-06-26  5:32 dpdklab
2024-06-26  5:32 dpdklab
2024-06-26  5:31 dpdklab
2024-06-26  5:31 dpdklab
2024-06-26  5:31 dpdklab
2024-06-26  5:31 dpdklab
2024-06-26  5:30 dpdklab
2024-06-26  5:30 dpdklab
2024-06-26  5:30 dpdklab
2024-06-26  5:30 dpdklab
2024-06-26  5:30 dpdklab
2024-06-26  5:29 dpdklab
2024-06-26  5:29 dpdklab
2024-06-26  5:29 dpdklab
2024-06-26  5:28 dpdklab
2024-06-26  5:28 dpdklab
2024-06-26  5:27 dpdklab
2024-06-26  5:27 dpdklab
2024-06-26  5:26 dpdklab
2024-06-26  5:26 dpdklab
2024-06-26  5:26 dpdklab
2024-06-26  5:25 dpdklab
2024-06-26  5:23 dpdklab
2024-06-26  5:23 dpdklab
2024-06-26  5:21 dpdklab
2024-06-26  5:21 dpdklab
2024-06-26  5:20 dpdklab
2024-06-26  5:18 dpdklab
2024-06-26  5:03 dpdklab
2024-06-26  4:57 dpdklab
2024-06-26  4:53 dpdklab
2024-06-26  4:53 dpdklab
2024-06-26  4:52 dpdklab
2024-06-26  4:48 dpdklab
2024-06-26  4:47 dpdklab
2024-06-26  4:30 dpdklab
2024-06-26  4:20 dpdklab
2024-06-26  4:19 dpdklab
2024-06-26  4:17 dpdklab
2024-06-26  4:16 dpdklab
2024-06-26  3:50 dpdklab
2024-06-26  3:47 dpdklab
2024-06-26  3:25 dpdklab
2024-06-26  3:25 dpdklab
2024-06-26  3:01 dpdklab
2024-06-26  2:53 dpdklab
2024-06-26  2:52 dpdklab
2024-06-26  2:10 dpdklab
2024-06-26  2:08 dpdklab
2024-06-26  2:08 dpdklab
2024-06-26  2:01 dpdklab
2024-06-26  1:59 dpdklab
2024-06-26  1:56 dpdklab
2024-06-26  1:55 dpdklab
2024-06-26  1:55 dpdklab
2024-06-26  1:54 dpdklab
2024-06-26  1:53 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=667b98cb.4a0a0220.18c56.7064SMTPIN_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).