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] b28984fcf6b69e90a917f51cf0f9139a9b74486a
Date: Sun, 13 Oct 2024 09:53:35 -0700 (PDT) [thread overview]
Message-ID: <670bfb0f.050a0220.28a1ca.01e6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
b28984fcf6b69e90a917f51cf0f9139a9b74486a --> testing pass
Upstream job id: Windows-Compile-DPDK-VS#3441
Test environment and result as below:
+---------------------+-----------------------+----------------------+-------------------+
| Environment | dpdk_win_llvm_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+=======================+======================+===================+
| Windows Server 2022 | PASS | PASS | 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/30993/
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-13 16:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-13 16:53 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-13 20:52 dpdklab
2024-10-13 17:10 dpdklab
2024-10-13 16:51 dpdklab
2024-10-13 11:22 dpdklab
2024-10-13 10:45 dpdklab
2024-10-13 10:39 dpdklab
2024-10-13 10:20 dpdklab
2024-10-13 9:18 dpdklab
2024-10-13 8:06 dpdklab
2024-10-13 7:56 dpdklab
2024-10-13 7:43 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=670bfb0f.050a0220.28a1ca.01e6SMTPIN_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).