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] 03d37ac13b61563fb31e4a0f5d0e427a61d548d5
Date: Fri, 18 Oct 2024 23:47:44 -0700 (PDT) [thread overview]
Message-ID: <67135610.170a0220.36fb15.746fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
03d37ac13b61563fb31e4a0f5d0e427a61d548d5 --> testing pass
Upstream job id: Windows-Compile-DPDK-VS#3542
Test environment and result as below:
+---------------------+--------------------+-------------------+
| Environment | dpdk_meson_compile | dpdk_msvc_compile |
+=====================+====================+===================+
| FreeBSD 13.4 | PASS | SKIPPED |
+---------------------+--------------------+-------------------+
| FreeBSD 14.1 | PASS | SKIPPED |
+---------------------+--------------------+-------------------+
| Windows Server 2022 | SKIPPED | PASS |
+---------------------+--------------------+-------------------+
FreeBSD 13.4
Kernel: 13.4-RELEASE-p1
Compiler: clang 18.1.6
FreeBSD 14.1
Kernel: 14.1-RELEASE-p3
Compiler: clang 18.1.5
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/31110/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-10-19 6:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-19 6:47 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-23 8:15 dpdklab
2024-10-22 8:43 dpdklab
2024-10-22 0:56 dpdklab
2024-10-19 9:13 dpdklab
2024-10-19 8:29 dpdklab
2024-10-19 5:31 dpdklab
2024-10-18 22:39 dpdklab
2024-10-18 12:53 dpdklab
2024-10-18 12:46 dpdklab
2024-10-18 12:13 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=67135610.170a0220.36fb15.746fSMTPIN_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).