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] e0f7ebe88ab4588dd352e9ec14270ce4e3b1470b
Date: Fri, 09 Aug 2024 23:47:44 -0700 (PDT) [thread overview]
Message-ID: <66b70d10.050a0220.30664c.28f8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
e0f7ebe88ab4588dd352e9ec14270ce4e3b1470b --> testing pass
Upstream job id: Windows-Compile-DPDK-Mingw64#21414
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| FreeBSD 13.3 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
FreeBSD 13.3
Kernel: 13.3-RELEASE-p1
Compiler: clang 17.0.6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/30200/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-08-10 6:47 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-10 6:47 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-10 17:31 dpdklab
2024-08-10 11:28 dpdklab
2024-08-10 10:36 dpdklab
2024-08-10 10:21 dpdklab
2024-08-10 10:13 dpdklab
2024-08-10 9:52 dpdklab
2024-08-10 8:27 dpdklab
2024-08-10 8:06 dpdklab
2024-08-10 8:01 dpdklab
2024-08-10 7:56 dpdklab
2024-08-10 7:51 dpdklab
2024-08-10 7:43 dpdklab
2024-08-10 7:16 dpdklab
2024-08-10 7:13 dpdklab
2024-08-10 7:09 dpdklab
2024-08-10 7:08 dpdklab
2024-08-10 7:07 dpdklab
2024-08-10 7:03 dpdklab
2024-08-10 6:55 dpdklab
2024-08-10 6:55 dpdklab
2024-08-10 6:50 dpdklab
2024-08-10 6:47 dpdklab
2024-08-10 6:47 dpdklab
2024-08-10 6:45 dpdklab
2024-08-10 1:37 dpdklab
2024-08-09 11:24 dpdklab
2024-08-09 11:17 dpdklab
2024-08-09 11:12 dpdklab
2024-08-09 11:07 dpdklab
2024-08-09 10:46 dpdklab
2024-08-09 9:04 dpdklab
2024-08-09 8:49 dpdklab
2024-08-09 8:49 dpdklab
2024-08-09 8:43 dpdklab
2024-08-09 8:38 dpdklab
2024-08-09 8:35 dpdklab
2024-08-09 8:30 dpdklab
2024-08-09 8:29 dpdklab
2024-08-09 8:26 dpdklab
2024-08-09 8:20 dpdklab
2024-08-09 8:20 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=66b70d10.050a0220.30664c.28f8SMTPIN_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).