From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Chenbo Xia <chenbox@nvidia.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: |SUCCESS| [GIT MASTER] d92688baedcfc963b7539899347012a09c45a15b
Date: Fri, 17 Jan 2025 23:19:14 -0800 (PST) [thread overview]
Message-ID: <678b55f2.170a0220.12f8cd.1b2aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-virtio
d92688baedcfc963b7539899347012a09c45a15b --> testing pass
Upstream job id: Windows-Compile-DPDK-VS#4651
Test environment and result as below:
+---------------------+-------------------+--------------------+
| Environment | dpdk_msvc_compile | dpdk_meson_compile |
+=====================+===================+====================+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+-------------------+--------------------+
| FreeBSD 13.4 | SKIPPED | PASS |
+---------------------+-------------------+--------------------+
| FreeBSD 14.2 | 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.4
Kernel: 13.4-RELEASE-p1
Compiler: clang 18.1.6
FreeBSD 14.2
Kernel: 14.2-RELEASE
Compiler: clang 18.1.6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/32251/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-01-18 7:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-18 7:19 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-18 10:36 dpdklab
2025-01-18 9:23 dpdklab
2025-01-18 9:09 dpdklab
2025-01-18 9:02 dpdklab
2025-01-18 8:09 dpdklab
2025-01-18 7:40 dpdklab
2025-01-18 7:21 dpdklab
2025-01-18 7:18 dpdklab
2025-01-18 7:16 dpdklab
2025-01-18 7:10 dpdklab
2025-01-18 7:10 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=678b55f2.170a0220.12f8cd.1b2aSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=chenbox@nvidia.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=maxime.coquelin@redhat.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).