From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] ff4d4839f9c2a6d05dca0a25ed6b1549402e1682
Date: Wed, 18 Sep 2024 00:35:31 -0700 (PDT) [thread overview]
Message-ID: <66ea82c3.170a0220.1ed1ec.2c24SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: tags/v22.11
ff4d4839f9c2a6d05dca0a25ed6b1549402e1682 --> testing pending
Upstream job id: Windows-Compile-DPDK-Native#22306
Test environment and result as below:
+---------------------+----------------------+-----------------------+--------------------+
| Environment | dpdk_mingw64_compile | dpdk_win_llvm_compile | dpdk_meson_compile |
+=====================+======================+=======================+====================+
| Windows Server 2022 | PASS | PEND | SKIPPED |
+---------------------+----------------------+-----------------------+--------------------+
| FreeBSD 13.3 | SKIPPED | SKIPPED | PEND |
+---------------------+----------------------+-----------------------+--------------------+
| FreeBSD 14.1 | SKIPPED | SKIPPED | PEND |
+---------------------+----------------------+-----------------------+--------------------+
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.3
Kernel: 13.3-RELEASE-p5
Compiler: clang 17.0.6
FreeBSD 14.1
Kernel: 14.1-RELEASE-p3
Compiler: clang 18.1.5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/30639/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-09-18 7:35 UTC|newest]
Thread overview: 164+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 7:35 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-27 7:09 dpdklab
2024-10-26 4:41 dpdklab
2024-10-26 1:59 dpdklab
2024-10-18 19:32 dpdklab
2024-10-18 9:05 dpdklab
2024-10-16 21:18 dpdklab
2024-10-16 20:55 dpdklab
2024-10-16 6:18 dpdklab
2024-10-14 15:33 dpdklab
2024-10-14 12:57 dpdklab
2024-10-14 12:54 dpdklab
2024-10-14 8:23 dpdklab
2024-10-13 13:50 dpdklab
2024-10-13 12:00 dpdklab
2024-10-13 11:44 dpdklab
2024-10-11 11:07 dpdklab
2024-10-11 5:48 dpdklab
2024-10-11 5:08 dpdklab
2024-10-10 11:59 dpdklab
2024-10-10 7:46 dpdklab
2024-10-10 6:33 dpdklab
2024-10-09 7:47 dpdklab
2024-10-09 7:22 dpdklab
2024-10-09 7:09 dpdklab
2024-10-08 7:00 dpdklab
2024-10-08 6:22 dpdklab
2024-10-08 6:12 dpdklab
2024-10-08 5:34 dpdklab
2024-10-07 8:10 dpdklab
2024-10-07 6:39 dpdklab
2024-10-07 5:48 dpdklab
2024-10-06 6:03 dpdklab
2024-10-06 5:41 dpdklab
2024-10-06 5:28 dpdklab
2024-10-06 5:02 dpdklab
2024-10-05 7:41 dpdklab
2024-10-05 6:52 dpdklab
2024-10-05 6:24 dpdklab
2024-10-05 6:12 dpdklab
2024-10-05 5:33 dpdklab
2024-10-04 10:03 dpdklab
2024-10-04 7:48 dpdklab
2024-10-04 7:46 dpdklab
2024-10-04 7:17 dpdklab
2024-10-04 5:52 dpdklab
2024-10-03 8:50 dpdklab
2024-10-03 6:36 dpdklab
2024-10-03 5:52 dpdklab
2024-10-03 5:39 dpdklab
2024-10-03 5:37 dpdklab
2024-10-01 5:43 dpdklab
2024-10-01 5:34 dpdklab
2024-10-01 5:23 dpdklab
2024-10-01 5:11 dpdklab
2024-09-30 9:02 dpdklab
2024-09-30 6:10 dpdklab
2024-09-30 6:03 dpdklab
2024-09-30 5:56 dpdklab
2024-09-30 5:48 dpdklab
2024-09-29 6:19 dpdklab
2024-09-29 6:07 dpdklab
2024-09-29 5:54 dpdklab
2024-09-29 5:16 dpdklab
2024-09-28 8:38 dpdklab
2024-09-28 6:05 dpdklab
2024-09-28 5:56 dpdklab
2024-09-28 5:26 dpdklab
2024-09-27 6:48 dpdklab
2024-09-27 6:16 dpdklab
2024-09-27 6:15 dpdklab
2024-09-27 5:59 dpdklab
2024-09-26 8:23 dpdklab
2024-09-26 7:04 dpdklab
2024-09-25 9:47 dpdklab
2024-09-25 6:15 dpdklab
2024-09-25 5:08 dpdklab
2024-09-24 6:04 dpdklab
2024-09-24 5:52 dpdklab
2024-09-24 5:10 dpdklab
2024-09-23 5:56 dpdklab
2024-09-23 5:50 dpdklab
2024-09-23 5:37 dpdklab
2024-09-23 5:24 dpdklab
2024-09-22 8:42 dpdklab
2024-09-22 5:57 dpdklab
2024-09-22 5:48 dpdklab
2024-09-22 5:33 dpdklab
2024-09-21 9:23 dpdklab
2024-09-21 7:13 dpdklab
2024-09-21 6:41 dpdklab
2024-09-20 7:46 dpdklab
2024-09-20 7:24 dpdklab
2024-09-20 7:18 dpdklab
2024-09-20 5:51 dpdklab
2024-09-19 16:17 dpdklab
2024-09-19 16:03 dpdklab
2024-09-19 13:46 dpdklab
2024-09-18 9:39 dpdklab
2024-09-18 7:25 dpdklab
2024-09-18 7:23 dpdklab
2024-09-17 6:52 dpdklab
2024-09-17 6:44 dpdklab
2024-09-16 6:28 dpdklab
2024-09-16 5:40 dpdklab
2024-09-16 5:08 dpdklab
2024-09-15 5:37 dpdklab
2024-09-15 5:32 dpdklab
2024-09-15 4:58 dpdklab
2024-09-14 5:47 dpdklab
2024-09-14 5:46 dpdklab
2024-09-14 5:38 dpdklab
2024-09-14 5:34 dpdklab
2024-09-13 6:50 dpdklab
2024-09-13 5:48 dpdklab
2024-09-13 5:13 dpdklab
2024-09-13 4:46 dpdklab
2024-09-12 14:12 dpdklab
2024-09-12 13:57 dpdklab
2024-09-12 13:29 dpdklab
2024-09-12 13:12 dpdklab
2024-09-11 13:22 dpdklab
2024-09-11 7:32 dpdklab
2024-09-11 7:23 dpdklab
2024-09-11 6:46 dpdklab
2024-09-10 14:32 dpdklab
2024-09-10 12:41 dpdklab
2024-09-10 12:22 dpdklab
2024-09-10 12:12 dpdklab
2024-09-10 6:38 dpdklab
2024-09-09 5:08 dpdklab
2024-09-09 4:41 dpdklab
2024-09-09 4:34 dpdklab
2024-09-09 4:33 dpdklab
2024-09-08 7:31 dpdklab
2024-09-08 5:21 dpdklab
2024-09-08 4:59 dpdklab
2024-09-08 4:50 dpdklab
2024-09-08 4:49 dpdklab
2024-09-07 10:56 dpdklab
2024-09-07 10:05 dpdklab
2024-09-07 5:12 dpdklab
2024-09-06 10:57 dpdklab
2024-09-05 9:33 dpdklab
2024-09-04 7:20 dpdklab
2024-09-03 7:15 dpdklab
2024-09-02 7:54 dpdklab
2024-09-01 7:21 dpdklab
2024-08-31 4:42 dpdklab
2024-08-30 6:53 dpdklab
2024-08-28 8:04 dpdklab
2024-08-28 7:48 dpdklab
2024-08-27 6:58 dpdklab
2024-08-26 9:34 dpdklab
2024-08-26 7:05 dpdklab
2024-08-25 8:58 dpdklab
2024-08-25 7:55 dpdklab
2024-08-24 11:02 dpdklab
2024-08-24 10:46 dpdklab
2024-08-23 7:15 dpdklab
2024-08-23 4:50 dpdklab
2024-08-22 7:14 dpdklab
2024-08-21 7:44 dpdklab
2024-08-21 7:08 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=66ea82c3.170a0220.1ed1ec.2c24SMTPIN_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).