From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 4dc4e33ffa108e945fc8a1e2bbc7819791faa61e
Date: Tue, 17 Dec 2024 23:07:11 -0800 (PST) [thread overview]
Message-ID: <6762749f.050a0220.34d605.9fcaSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
4dc4e33ffa108e945fc8a1e2bbc7819791faa61e --> testing pass
Upstream job id: Generic-DPDK-Compile-Meson#344324
Test environment and result as below:
+-------------------+--------------------+------------------+-------------------+
| Environment | dpdk_meson_compile | dpdk_compile_ovs | dpdk_compile_spdk |
+===================+====================+==================+===================+
| Fedora 39 (Clang) | PASS | PASS | PASS |
+-------------------+--------------------+------------------+-------------------+
| Fedora 39 | PASS | PASS | PASS |
+-------------------+--------------------+------------------+-------------------+
Fedora 39 (Clang)
Kernel: Depends on container host
Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/31960/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-12-18 7:07 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 7:07 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-18 17:40 dpdklab
2024-12-18 17:28 dpdklab
2024-12-18 15:02 dpdklab
2024-12-18 12:55 dpdklab
2024-12-18 11:05 dpdklab
2024-12-18 11:00 dpdklab
2024-12-18 10:02 dpdklab
2024-12-18 9:38 dpdklab
2024-12-18 9:09 dpdklab
2024-12-18 9:08 dpdklab
2024-12-18 7:05 dpdklab
2024-12-18 7:00 dpdklab
2024-12-18 6:58 dpdklab
2024-12-18 5:15 dpdklab
2024-12-18 5:01 dpdklab
2024-12-18 4:11 dpdklab
2024-12-18 4:09 dpdklab
2024-12-18 3:19 dpdklab
2024-12-18 2:39 dpdklab
2024-12-18 1:54 dpdklab
2024-12-18 1:54 dpdklab
2024-12-18 1:43 dpdklab
2024-12-18 1:35 dpdklab
2024-12-18 1:20 dpdklab
2024-12-18 1:12 dpdklab
2024-12-18 0:57 dpdklab
2024-12-18 0:42 dpdklab
2024-12-18 0:11 dpdklab
2024-12-17 23:56 dpdklab
2024-12-17 23:48 dpdklab
2024-12-17 23:36 dpdklab
2024-12-17 22:37 dpdklab
2024-12-17 22:26 dpdklab
2024-12-17 22:24 dpdklab
2024-12-17 22:10 dpdklab
2024-12-17 22:05 dpdklab
2024-12-17 22:04 dpdklab
2024-12-17 22:01 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=6762749f.050a0220.34d605.9fcaSMTPIN_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).