From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] b0fd604534d435cad3ac75fe4fb96b0841084af3
Date: Tue, 09 Jul 2024 03:53:25 -0700 (PDT) [thread overview]
Message-ID: <668d16a5.050a0220.c31b9.5a27SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: dpdk-next-net
b0fd604534d435cad3ac75fe4fb96b0841084af3 --> testing pending
Test environment and result as below:
+---------------------+--------------------+-------------------+
| Environment | dpdk_meson_compile | dpdk_msvc_compile |
+=====================+====================+===================+
| FreeBSD 13.3 | PASS | SKIPPED |
+---------------------+--------------------+-------------------+
| FreeBSD 14.1 | PEND | SKIPPED |
+---------------------+--------------------+-------------------+
| Windows Server 2022 | PEND | PASS |
+---------------------+--------------------+-------------------+
FreeBSD 13.3
Kernel: 13.3-RELEASE-p1
Compiler: clang 17.0.6
FreeBSD 14.1
Kernel: 14.1
Compiler: clang 18.1.5
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29787/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-07-09 10:53 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 10:53 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-09 23:02 dpdklab
2024-07-09 22:58 dpdklab
2024-07-09 22:54 dpdklab
2024-07-09 22:52 dpdklab
2024-07-09 22:39 dpdklab
2024-07-09 22:36 dpdklab
2024-07-09 22:33 dpdklab
2024-07-09 22:15 dpdklab
2024-07-09 22:14 dpdklab
2024-07-09 22:14 dpdklab
2024-07-09 22:05 dpdklab
2024-07-09 22:04 dpdklab
2024-07-09 22:02 dpdklab
2024-07-09 21:55 dpdklab
2024-07-09 21:50 dpdklab
2024-07-09 21:49 dpdklab
2024-07-09 17:21 dpdklab
2024-07-09 17:17 dpdklab
2024-07-09 17:15 dpdklab
2024-07-09 17:13 dpdklab
2024-07-09 17:07 dpdklab
2024-07-09 17:07 dpdklab
2024-07-09 17:05 dpdklab
2024-07-09 16:58 dpdklab
2024-07-09 16:57 dpdklab
2024-07-09 16:47 dpdklab
2024-07-09 16:45 dpdklab
2024-07-09 16:44 dpdklab
2024-07-09 16:33 dpdklab
2024-07-09 16:31 dpdklab
2024-07-09 16:27 dpdklab
2024-07-09 16:13 dpdklab
2024-07-09 16:11 dpdklab
2024-07-09 11:38 dpdklab
2024-07-09 11:21 dpdklab
2024-07-09 11:12 dpdklab
2024-07-09 11:00 dpdklab
2024-07-09 10:58 dpdklab
2024-07-09 10:56 dpdklab
2024-07-09 10:50 dpdklab
2024-07-09 9:46 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=668d16a5.050a0220.c31b9.5a27SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).