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] 9d2cc6c2419de6d6079322f1efd8c5ad20410b86
Date: Wed, 22 Nov 2023 08:46:34 -0800 (PST) [thread overview]
Message-ID: <655e306a.250a0220.8634f.42caSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: 21.11-staging
9d2cc6c2419de6d6079322f1efd8c5ad20410b86 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
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/27076/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-22 16:46 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 16:46 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-22 18:47 dpdklab
2023-11-22 18:42 dpdklab
2023-11-22 18:19 dpdklab
2023-11-22 18:11 dpdklab
2023-11-22 18:07 dpdklab
2023-11-22 18:07 dpdklab
2023-11-22 17:44 dpdklab
2023-11-22 17:42 dpdklab
2023-11-22 17:42 dpdklab
2023-11-22 17:40 dpdklab
2023-11-22 17:40 dpdklab
2023-11-22 17:39 dpdklab
2023-11-22 17:38 dpdklab
2023-11-22 17:37 dpdklab
2023-11-22 17:37 dpdklab
2023-11-22 17:36 dpdklab
2023-11-22 17:36 dpdklab
2023-11-22 17:34 dpdklab
2023-11-22 17:32 dpdklab
2023-11-22 17:31 dpdklab
2023-11-22 17:30 dpdklab
2023-11-22 17:29 dpdklab
2023-11-22 17:29 dpdklab
2023-11-22 17:29 dpdklab
2023-11-22 17:20 dpdklab
2023-11-22 17:11 dpdklab
2023-11-22 17:06 dpdklab
2023-11-22 17:04 dpdklab
2023-11-22 17:04 dpdklab
2023-11-22 17:03 dpdklab
2023-11-22 17:03 dpdklab
2023-11-22 16:58 dpdklab
2023-11-22 16:58 dpdklab
2023-11-22 16:56 dpdklab
2023-11-22 16:55 dpdklab
2023-11-22 16:55 dpdklab
2023-11-22 16:55 dpdklab
2023-11-22 16:54 dpdklab
2023-11-22 16:53 dpdklab
2023-11-22 16:50 dpdklab
2023-11-22 16:50 dpdklab
2023-11-22 16:46 dpdklab
2023-11-22 16:46 dpdklab
2023-11-22 16:45 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=655e306a.250a0220.8634f.42caSMTPIN_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).