From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] d58c97481a136ad5342c9d8717b22bdaa5eccd43
Date: Tue, 26 Sep 2023 18:08:23 -0700 (PDT) [thread overview]
Message-ID: <65138087.170a0220.37b3a.9626SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
d58c97481a136ad5342c9d8717b22bdaa5eccd43 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Buster | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | SKIPPED | PASS |
+---------------------+--------------------+----------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/26255/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-27 1:08 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 1:08 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-27 11:33 dpdklab
2023-09-27 4:03 dpdklab
2023-09-27 4:01 dpdklab
2023-09-27 3:59 dpdklab
2023-09-27 3:57 dpdklab
2023-09-27 3:55 dpdklab
2023-09-27 3:53 dpdklab
2023-09-27 3:44 dpdklab
2023-09-27 3:42 dpdklab
2023-09-27 3:32 dpdklab
2023-09-27 3:28 dpdklab
2023-09-27 3:24 dpdklab
2023-09-27 2:28 dpdklab
2023-09-27 2:10 dpdklab
2023-09-27 2:02 dpdklab
2023-09-27 1:52 dpdklab
2023-09-27 1:50 dpdklab
2023-09-27 1:38 dpdklab
2023-09-27 1:37 dpdklab
2023-09-27 1:23 dpdklab
2023-09-27 1:22 dpdklab
2023-09-27 1:20 dpdklab
2023-09-27 1:18 dpdklab
2023-09-27 1:18 dpdklab
2023-09-27 1:18 dpdklab
2023-09-27 1:17 dpdklab
2023-09-27 1:16 dpdklab
2023-09-27 1:15 dpdklab
2023-09-27 1:13 dpdklab
2023-09-27 1:13 dpdklab
2023-09-27 1:12 dpdklab
2023-09-27 1:12 dpdklab
2023-09-27 1:11 dpdklab
2023-09-27 1:11 dpdklab
2023-09-27 1:10 dpdklab
2023-09-27 1:10 dpdklab
2023-09-27 1:09 dpdklab
2023-09-27 1:09 dpdklab
2023-09-27 1:08 dpdklab
2023-09-27 1:07 dpdklab
2023-09-27 1:07 dpdklab
2023-09-27 1:06 dpdklab
2023-09-27 1:06 dpdklab
2023-09-27 1:06 dpdklab
2023-09-27 1:05 dpdklab
2023-09-27 0:58 dpdklab
2023-09-26 15:17 dpdklab
2023-09-26 14:59 dpdklab
2023-09-26 14:59 dpdklab
2023-09-26 14:45 dpdklab
2023-09-26 1:44 dpdklab
2023-09-26 1:40 dpdklab
2023-09-26 1:36 dpdklab
2023-09-26 1:33 dpdklab
2023-09-26 1:29 dpdklab
2023-09-26 1:28 dpdklab
2023-09-26 1:25 dpdklab
2023-09-26 1:25 dpdklab
2023-09-26 1:24 dpdklab
2023-09-26 1:21 dpdklab
2023-09-26 1:17 dpdklab
2023-09-26 1:17 dpdklab
2023-09-26 1:17 dpdklab
2023-09-26 1:16 dpdklab
2023-09-26 1:12 dpdklab
2023-09-26 1:07 dpdklab
2023-09-26 1:05 dpdklab
2023-09-26 1:04 dpdklab
2023-09-26 1:04 dpdklab
2023-09-26 1:03 dpdklab
2023-09-26 1:03 dpdklab
2023-09-26 1:03 dpdklab
2023-09-26 1:03 dpdklab
2023-09-26 1:02 dpdklab
2023-09-26 1:02 dpdklab
2023-09-26 1:02 dpdklab
2023-09-26 1:02 dpdklab
2023-09-26 1:02 dpdklab
2023-09-26 1:02 dpdklab
2023-09-26 1:02 dpdklab
2023-09-26 1:02 dpdklab
2023-09-26 1:02 dpdklab
2023-09-26 1:01 dpdklab
2023-09-26 1:01 dpdklab
2023-09-26 1:01 dpdklab
2023-09-26 1:01 dpdklab
2023-09-26 1:00 dpdklab
2023-09-26 1:00 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=65138087.170a0220.37b3a.9626SMTPIN_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).