From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 3bcd5b3198d4a31176b1ac73fc7236a12186fffe
Date: Wed, 04 Oct 2023 18:32:06 -0700 (PDT) [thread overview]
Message-ID: <651e1216.630a0220.6ef8a.104dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
3bcd5b3198d4a31176b1ac73fc7236a12186fffe --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/26356/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-05 1:32 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 1:32 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-06 2:52 dpdklab
2023-10-06 2:19 dpdklab
2023-10-06 2:18 dpdklab
2023-10-06 2:17 dpdklab
2023-10-06 2:14 dpdklab
2023-10-06 2:10 dpdklab
2023-10-06 2:07 dpdklab
2023-10-06 2:06 dpdklab
2023-10-06 2:03 dpdklab
2023-10-06 2:00 dpdklab
2023-10-06 1:57 dpdklab
2023-10-06 1:55 dpdklab
2023-10-06 1:53 dpdklab
2023-10-06 1:53 dpdklab
2023-10-06 1:50 dpdklab
2023-10-06 1:50 dpdklab
2023-10-06 1:49 dpdklab
2023-10-06 1:49 dpdklab
2023-10-06 1:49 dpdklab
2023-10-06 1:48 dpdklab
2023-10-06 1:48 dpdklab
2023-10-06 1:48 dpdklab
2023-10-06 1:48 dpdklab
2023-10-06 1:48 dpdklab
2023-10-06 1:48 dpdklab
2023-10-06 1:47 dpdklab
2023-10-06 1:47 dpdklab
2023-10-06 1:47 dpdklab
2023-10-06 1:47 dpdklab
2023-10-06 1:46 dpdklab
2023-10-06 1:46 dpdklab
2023-10-06 1:46 dpdklab
2023-10-06 1:45 dpdklab
2023-10-06 1:45 dpdklab
2023-10-06 1:45 dpdklab
2023-10-06 1:44 dpdklab
2023-10-06 1:44 dpdklab
2023-10-06 1:44 dpdklab
2023-10-06 1:43 dpdklab
2023-10-06 1:43 dpdklab
2023-10-06 1:43 dpdklab
2023-10-06 1:43 dpdklab
2023-10-06 1:42 dpdklab
2023-10-06 1:42 dpdklab
2023-10-06 1:42 dpdklab
2023-10-06 1:41 dpdklab
2023-10-06 1:40 dpdklab
2023-10-06 1:40 dpdklab
2023-10-05 2:18 dpdklab
2023-10-05 2:03 dpdklab
2023-10-05 2:02 dpdklab
2023-10-05 2:00 dpdklab
2023-10-05 1:58 dpdklab
2023-10-05 1:56 dpdklab
2023-10-05 1:54 dpdklab
2023-10-05 1:51 dpdklab
2023-10-05 1:50 dpdklab
2023-10-05 1:44 dpdklab
2023-10-05 1:43 dpdklab
2023-10-05 1:36 dpdklab
2023-10-05 1:29 dpdklab
2023-10-05 1:28 dpdklab
2023-10-05 1:28 dpdklab
2023-10-05 1:27 dpdklab
2023-10-05 1:22 dpdklab
2023-10-05 1:19 dpdklab
2023-10-05 1:18 dpdklab
2023-10-05 1:14 dpdklab
2023-10-05 1:13 dpdklab
2023-10-05 1:10 dpdklab
2023-10-05 1:08 dpdklab
2023-10-05 1:08 dpdklab
2023-10-05 1:08 dpdklab
2023-10-05 1:08 dpdklab
2023-10-05 1:08 dpdklab
2023-10-05 1:07 dpdklab
2023-10-05 1:07 dpdklab
2023-10-05 1:06 dpdklab
2023-10-05 1:06 dpdklab
2023-10-05 1:06 dpdklab
2023-10-05 1:05 dpdklab
2023-10-05 1:04 dpdklab
2023-10-05 1:04 dpdklab
2023-10-05 1:03 dpdklab
2023-10-05 1:02 dpdklab
2023-10-05 1:02 dpdklab
2023-10-05 1:01 dpdklab
2023-10-05 1:01 dpdklab
2023-10-05 1:01 dpdklab
2023-10-05 1:00 dpdklab
2023-10-05 0:59 dpdklab
2023-10-05 0:59 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=651e1216.630a0220.6ef8a.104dSMTPIN_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).