From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Jerin Jacob <jerinj@marvell.com>
Subject: |SUCCESS| [GIT MASTER] c15902587b538ff02cfb0fbb4dd481f1503d936b
Date: Tue, 16 Jul 2024 12:56:27 -0700 (PDT) [thread overview]
Message-ID: <6696d06b.050a0220.f85b.1aefSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-eventdev
c15902587b538ff02cfb0fbb4dd481f1503d936b --> testing pass
Test environment and result as below:
+---------------------+----------------------+
| Environment | dpdk_mingw64_compile |
+=====================+======================+
| Windows Server 2019 | PASS |
+---------------------+----------------------+
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29646/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-07-16 19:56 UTC|newest]
Thread overview: 187+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 19:56 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-16 12:11 dpdklab
2024-07-16 10:20 dpdklab
2024-07-16 10:00 dpdklab
2024-07-16 9:55 dpdklab
2024-07-16 9:26 dpdklab
2024-07-16 9:21 dpdklab
2024-07-16 9:00 dpdklab
2024-07-16 8:55 dpdklab
2024-07-16 8:34 dpdklab
2024-07-16 8:30 dpdklab
2024-07-16 5:19 dpdklab
2024-07-15 21:33 dpdklab
2024-07-15 20:49 dpdklab
2024-07-15 20:48 dpdklab
2024-07-15 20:45 dpdklab
2024-07-15 19:36 dpdklab
2024-07-15 19:26 dpdklab
2024-07-15 19:10 dpdklab
2024-07-15 18:42 dpdklab
2024-07-15 18:31 dpdklab
2024-07-15 17:49 dpdklab
2024-07-15 17:09 dpdklab
2024-07-15 16:52 dpdklab
2024-07-15 16:06 dpdklab
2024-07-15 15:56 dpdklab
2024-07-15 15:52 dpdklab
2024-07-15 15:45 dpdklab
2024-07-15 15:42 dpdklab
2024-07-15 15:33 dpdklab
2024-07-15 15:28 dpdklab
2024-07-15 15:17 dpdklab
2024-07-15 15:17 dpdklab
2024-07-15 15:09 dpdklab
2024-07-15 15:07 dpdklab
2024-07-15 15:06 dpdklab
2024-07-15 14:59 dpdklab
2024-07-15 14:54 dpdklab
2024-07-15 14:53 dpdklab
2024-07-15 14:46 dpdklab
2024-07-15 14:45 dpdklab
2024-07-03 5:44 dpdklab
2024-07-03 3:54 dpdklab
2024-07-02 21:58 dpdklab
2024-07-02 21:58 dpdklab
2024-07-02 21:27 dpdklab
2024-07-02 21:13 dpdklab
2024-07-02 20:43 dpdklab
2024-07-02 20:08 dpdklab
2024-07-02 19:54 dpdklab
2024-07-02 18:58 dpdklab
2024-07-02 17:24 dpdklab
2024-07-02 17:16 dpdklab
2024-07-02 17:12 dpdklab
2024-07-02 16:56 dpdklab
2024-07-02 16:53 dpdklab
2024-07-02 16:52 dpdklab
2024-07-02 16:51 dpdklab
2024-07-02 16:48 dpdklab
2024-07-02 16:46 dpdklab
2024-06-30 2:04 dpdklab
2024-06-30 2:01 dpdklab
2024-06-30 1:12 dpdklab
2024-06-30 1:09 dpdklab
2024-06-30 1:06 dpdklab
2024-06-30 1:06 dpdklab
2024-06-30 1:01 dpdklab
2024-06-30 0:57 dpdklab
2024-06-30 0:53 dpdklab
2024-06-30 0:43 dpdklab
2024-06-30 0:35 dpdklab
2024-06-30 0:33 dpdklab
2024-06-30 0:26 dpdklab
2024-06-30 0:25 dpdklab
2024-06-29 21:16 dpdklab
2024-06-29 19:38 dpdklab
2024-06-29 17:37 dpdklab
2024-06-29 17:33 dpdklab
2024-06-29 17:25 dpdklab
2024-06-29 17:20 dpdklab
2024-06-29 17:11 dpdklab
2024-06-29 17:08 dpdklab
2024-06-29 17:04 dpdklab
2024-06-29 17:01 dpdklab
2024-06-29 16:52 dpdklab
2024-06-29 16:52 dpdklab
2024-06-29 16:48 dpdklab
2024-06-29 16:46 dpdklab
2024-06-29 7:44 dpdklab
2024-06-28 21:02 dpdklab
2024-06-28 20:43 dpdklab
2024-06-28 10:36 dpdklab
2024-06-28 10:36 dpdklab
2024-06-28 10:33 dpdklab
2024-06-28 10:29 dpdklab
2024-06-28 10:28 dpdklab
2024-06-28 10:24 dpdklab
2024-06-28 10:22 dpdklab
2024-06-28 10:20 dpdklab
2024-06-28 10:14 dpdklab
2024-06-28 9:59 dpdklab
2024-06-28 9:50 dpdklab
2024-06-28 9:48 dpdklab
2024-06-28 9:46 dpdklab
2024-06-28 9:42 dpdklab
2024-06-28 9:41 dpdklab
2024-06-28 9:38 dpdklab
2024-06-28 9:18 dpdklab
2024-06-28 9:15 dpdklab
2024-06-28 8:48 dpdklab
2024-06-28 8:38 dpdklab
2024-06-28 8:36 dpdklab
2024-06-28 8:36 dpdklab
2024-06-28 8:36 dpdklab
2024-06-28 8:35 dpdklab
2024-06-28 8:34 dpdklab
2024-06-28 8:33 dpdklab
2024-06-28 8:31 dpdklab
2024-06-28 8:30 dpdklab
2024-06-28 8:29 dpdklab
2024-06-28 8:29 dpdklab
2024-06-28 8:22 dpdklab
2024-06-28 8:20 dpdklab
2024-06-28 8:18 dpdklab
2024-06-28 8:17 dpdklab
2024-06-28 8:15 dpdklab
2024-06-28 8:13 dpdklab
2024-06-28 8:07 dpdklab
2024-06-28 8:06 dpdklab
2024-06-28 8:01 dpdklab
2024-06-28 7:54 dpdklab
2024-06-28 7:53 dpdklab
2024-06-28 7:23 dpdklab
2024-06-28 7:21 dpdklab
2024-06-28 7:21 dpdklab
2024-06-28 7:17 dpdklab
2024-06-28 7:14 dpdklab
2024-06-28 7:14 dpdklab
2024-06-28 7:09 dpdklab
2024-06-28 7:06 dpdklab
2024-06-28 7:05 dpdklab
2024-06-28 7:05 dpdklab
2024-06-28 7:00 dpdklab
2024-06-28 6:35 dpdklab
2024-06-28 6:30 dpdklab
2024-06-28 5:58 dpdklab
2024-06-28 5:48 dpdklab
2024-06-28 5:45 dpdklab
2024-06-28 5:44 dpdklab
2024-06-28 5:44 dpdklab
2024-06-28 5:42 dpdklab
2024-06-28 5:40 dpdklab
2024-06-28 5:38 dpdklab
2024-06-28 5:36 dpdklab
2024-06-28 5:33 dpdklab
2024-06-28 5:30 dpdklab
2024-06-28 5:26 dpdklab
2024-06-28 5:24 dpdklab
2024-06-28 5:17 dpdklab
2024-06-28 5:12 dpdklab
2024-06-28 5:11 dpdklab
2024-06-28 5:09 dpdklab
2024-06-28 5:08 dpdklab
2024-06-28 5:04 dpdklab
2024-06-28 5:04 dpdklab
2024-06-28 4:55 dpdklab
2024-06-28 4:35 dpdklab
2024-06-28 3:26 dpdklab
2024-06-28 2:51 dpdklab
2024-06-28 2:44 dpdklab
2024-06-28 2:11 dpdklab
2024-06-28 1:56 dpdklab
2024-06-28 1:45 dpdklab
2024-06-28 1:43 dpdklab
2024-06-28 1:39 dpdklab
2024-06-28 1:39 dpdklab
2024-06-28 1:38 dpdklab
2024-06-28 1:35 dpdklab
2024-06-28 1:34 dpdklab
2024-06-28 1:34 dpdklab
2024-06-28 1:30 dpdklab
2024-06-28 1:29 dpdklab
2024-06-28 1:26 dpdklab
2024-06-28 1:20 dpdklab
2024-06-28 1:16 dpdklab
2024-06-28 1:15 dpdklab
2024-06-28 1:12 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=6696d06b.050a0220.f85b.1aefSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=jerinj@marvell.com \
--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).