From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] aa0655d5f18f1a185b1b334f4a7e166b85912eda
Date: Tue, 09 Jul 2024 04:21:01 -0700 (PDT) [thread overview]
Message-ID: <668d1d1d.050a0220.2e3bc.5f55SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: 23.11-staging
aa0655d5f18f1a185b1b334f4a7e166b85912eda --> testing pending
Test environment and result as below:
+---------------------+--------------------+----------------------+-------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+====================+======================+===================+
| Windows Server 2022 | PEND | PASS | PEND |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 13.3 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 14.1 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2019 | PEND | PEND | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
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 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29788/
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 11:21 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 11:21 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-10 2:17 dpdklab
2024-07-10 2:13 dpdklab
2024-07-10 2:03 dpdklab
2024-07-10 1:59 dpdklab
2024-07-10 1:55 dpdklab
2024-07-10 1:52 dpdklab
2024-07-10 1:43 dpdklab
2024-07-10 1:35 dpdklab
2024-07-10 1:29 dpdklab
2024-07-10 1:26 dpdklab
2024-07-10 1:24 dpdklab
2024-07-10 0:38 dpdklab
2024-07-10 0:23 dpdklab
2024-07-10 0:14 dpdklab
2024-07-10 0:13 dpdklab
2024-07-10 0:12 dpdklab
2024-07-10 0:07 dpdklab
2024-07-10 0:02 dpdklab
2024-07-10 0:01 dpdklab
2024-07-10 0:00 dpdklab
2024-07-10 0:00 dpdklab
2024-07-09 23:58 dpdklab
2024-07-09 23:55 dpdklab
2024-07-09 23:51 dpdklab
2024-07-09 23:48 dpdklab
2024-07-09 23:48 dpdklab
2024-07-09 23:46 dpdklab
2024-07-09 23:46 dpdklab
2024-07-09 23:45 dpdklab
2024-07-09 23:45 dpdklab
2024-07-09 23:44 dpdklab
2024-07-09 23:42 dpdklab
2024-07-09 23:38 dpdklab
2024-07-09 23:18 dpdklab
2024-07-09 23:16 dpdklab
2024-07-09 23:12 dpdklab
2024-07-09 23:12 dpdklab
2024-07-09 22:53 dpdklab
2024-07-09 22:49 dpdklab
2024-07-09 22:43 dpdklab
2024-07-09 22:38 dpdklab
2024-07-09 22:21 dpdklab
2024-07-09 22:18 dpdklab
2024-07-09 22:13 dpdklab
2024-07-09 22:08 dpdklab
2024-07-09 18:38 dpdklab
2024-07-09 18:38 dpdklab
2024-07-09 18:25 dpdklab
2024-07-09 18:25 dpdklab
2024-07-09 18:24 dpdklab
2024-07-09 18:22 dpdklab
2024-07-09 18:09 dpdklab
2024-07-09 18:08 dpdklab
2024-07-09 18:06 dpdklab
2024-07-09 18:02 dpdklab
2024-07-09 17:56 dpdklab
2024-07-09 17:54 dpdklab
2024-07-09 17:45 dpdklab
2024-07-09 17:45 dpdklab
2024-07-09 17:39 dpdklab
2024-07-09 17:34 dpdklab
2024-07-09 17:30 dpdklab
2024-07-09 12:10 dpdklab
2024-07-09 11:47 dpdklab
2024-07-09 11:40 dpdklab
2024-07-09 11:27 dpdklab
2024-07-09 11:26 dpdklab
2024-07-09 11:25 dpdklab
2024-07-09 11:18 dpdklab
2024-07-09 11:16 dpdklab
2024-07-09 11:02 dpdklab
2024-07-09 10:35 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=668d1d1d.050a0220.2e3bc.5f55SMTPIN_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).