From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] c4b6f6ff54c32e922971e1403f19aba9ea614896
Date: Sat, 26 Apr 2025 22:39:25 -0700 (PDT) [thread overview]
Message-ID: <680dc30d.810a0220.9f28f.9b19SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: tags/v23.11
c4b6f6ff54c32e922971e1403f19aba9ea614896 --> testing pass
Upstream job id: Generic-VM-DPDK-Compile-Meson#34946
Test environment and result as below:
+---------------------+--------------------+-------------------+
| Environment | dpdk_meson_compile | dpdk_msvc_compile |
+=====================+====================+===================+
| Ubuntu 20.04 | PASS | SKIPPED |
+---------------------+--------------------+-------------------+
| FreeBSD 13.5 | PASS | SKIPPED |
+---------------------+--------------------+-------------------+
| FreeBSD 14.2 | PASS | SKIPPED |
+---------------------+--------------------+-------------------+
| Windows Server 2022 | SKIPPED | PASS |
+---------------------+--------------------+-------------------+
Ubuntu 20.04
Kernel: 4.19.325-0419325-generic
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
FreeBSD 13.5
Kernel: 13.5-RELEASE
Compiler: clang 19.1.7
FreeBSD 14.2
Kernel: 14.2-RELEASE
Compiler: clang 18.1.6
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/33367/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-04-27 5:39 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-27 5:39 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-27 15:21 dpdklab
2025-04-27 11:22 dpdklab
2025-04-27 11:21 dpdklab
2025-04-27 11:15 dpdklab
2025-04-27 7:57 dpdklab
2025-04-27 5:26 dpdklab
2025-04-27 5:09 dpdklab
2025-04-27 4:52 dpdklab
2025-04-27 4:49 dpdklab
2025-04-27 4:41 dpdklab
2025-04-27 4:39 dpdklab
2025-04-27 4:33 dpdklab
2025-04-27 4:30 dpdklab
2025-04-27 4:23 dpdklab
2025-04-26 9:41 dpdklab
2025-04-26 8:14 dpdklab
2025-04-26 7:57 dpdklab
2025-04-26 6:46 dpdklab
2025-04-26 6:41 dpdklab
2025-04-26 5:45 dpdklab
2025-04-26 5:45 dpdklab
2025-04-26 5:40 dpdklab
2025-04-26 5:35 dpdklab
2025-04-26 5:13 dpdklab
2025-04-26 5:07 dpdklab
2025-04-26 5:06 dpdklab
2025-04-26 5:01 dpdklab
2025-04-26 4:45 dpdklab
2025-04-26 4:39 dpdklab
2025-04-26 4:28 dpdklab
2025-04-25 11:07 dpdklab
2025-04-25 10:12 dpdklab
2025-04-25 10:11 dpdklab
2025-04-25 10:11 dpdklab
2025-04-24 10:02 dpdklab
2025-04-24 8:56 dpdklab
2025-04-24 8:29 dpdklab
2025-04-24 7:33 dpdklab
2025-04-24 7:16 dpdklab
2025-04-24 6:33 dpdklab
2025-04-24 4:57 dpdklab
2025-04-24 4:50 dpdklab
2025-04-24 4:45 dpdklab
2025-04-24 4:40 dpdklab
2025-04-24 4:39 dpdklab
2025-04-24 4:31 dpdklab
2025-04-24 4:25 dpdklab
2025-04-24 4:24 dpdklab
2025-04-23 9:34 dpdklab
2025-04-23 9:33 dpdklab
2025-04-23 9:13 dpdklab
2025-04-23 8:07 dpdklab
2025-04-23 8:05 dpdklab
2025-04-23 6:37 dpdklab
2025-04-23 6:16 dpdklab
2025-04-23 6:11 dpdklab
2025-04-23 5:44 dpdklab
2025-04-23 5:33 dpdklab
2025-04-23 5:01 dpdklab
2025-04-23 4:54 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=680dc30d.810a0220.9f28f.9b19SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).