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] e3f198f86b6bda1743a204e6daf98fc52f31e3fa
Date: Fri, 23 Aug 2024 00:51:13 -0700 (PDT)	[thread overview]
Message-ID: <66c83f71.050a0220.23c58d.7564SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-net

e3f198f86b6bda1743a204e6daf98fc52f31e3fa --> testing pass

Upstream job id: Windows-Compile-DPDK-Native#21666

Test environment and result as below:

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


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

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

FreeBSD 14.1
	Kernel: 14.1-RELEASE-p3
	Compiler: clang 18.1.5

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-08-23  7:51 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-23  7:51 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-21 22:48 dpdklab
2024-09-20 22:18 dpdklab
2024-08-23 15:04 dpdklab
2024-08-23 13:12 dpdklab
2024-08-23 13:08 dpdklab
2024-08-23 11:58 dpdklab
2024-08-23 11:58 dpdklab
2024-08-23 11:56 dpdklab
2024-08-23 11:54 dpdklab
2024-08-23 11:39 dpdklab
2024-08-23 11:37 dpdklab
2024-08-23 11:34 dpdklab
2024-08-23 11:34 dpdklab
2024-08-23 11:33 dpdklab
2024-08-23 11:33 dpdklab
2024-08-23 11:31 dpdklab
2024-08-23 11:31 dpdklab
2024-08-23 11:30 dpdklab
2024-08-23 11:28 dpdklab
2024-08-23 11:28 dpdklab
2024-08-23 11:27 dpdklab
2024-08-23  8:43 dpdklab
2024-08-23  8:35 dpdklab
2024-08-23  8:33 dpdklab
2024-08-23  8:26 dpdklab
2024-08-23  8:13 dpdklab
2024-08-23  8:06 dpdklab
2024-08-23  8:02 dpdklab
2024-08-23  7:57 dpdklab
2024-08-23  7:57 dpdklab
2024-08-23  7:57 dpdklab
2024-08-23  7:56 dpdklab
2024-08-23  7:54 dpdklab
2024-08-23  7:52 dpdklab
2024-08-23  7:51 dpdklab
2024-08-23  7:48 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=66c83f71.050a0220.23c58d.7564SMTPIN_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).