From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Qi Zhang <qi.z.zhang@intel.com>
Subject: |SUCCESS| [GIT MASTER] 4a343f542828a6c41edb473718dbb55b43f84dbe
Date: Wed, 27 Sep 2023 16:48:50 -0700 (PDT) [thread overview]
Message-ID: <6514bf62.170a0220.e5ac8.4c05SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net-intel
4a343f542828a6c41edb473718dbb55b43f84dbe --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Debian Buster | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
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/26270/
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 23:48 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 23:48 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-28 0:50 dpdklab
2023-09-28 0:13 dpdklab
2023-09-28 0:08 dpdklab
2023-09-28 0:04 dpdklab
2023-09-28 0:04 dpdklab
2023-09-28 0:02 dpdklab
2023-09-28 0:00 dpdklab
2023-09-27 23:58 dpdklab
2023-09-27 23:56 dpdklab
2023-09-27 23:52 dpdklab
2023-09-27 23:50 dpdklab
2023-09-27 23:46 dpdklab
2023-09-27 23:46 dpdklab
2023-09-27 23:39 dpdklab
2023-09-27 23:39 dpdklab
2023-09-27 23:39 dpdklab
2023-09-27 23:38 dpdklab
2023-09-27 23:38 dpdklab
2023-09-27 23:37 dpdklab
2023-09-27 23:37 dpdklab
2023-09-27 23:37 dpdklab
2023-09-27 23:37 dpdklab
2023-09-27 23:37 dpdklab
2023-09-27 23:36 dpdklab
2023-09-27 23:36 dpdklab
2023-09-27 23:36 dpdklab
2023-09-27 23:36 dpdklab
2023-09-27 23:35 dpdklab
2023-09-27 23:35 dpdklab
2023-09-27 23:35 dpdklab
2023-09-27 23:34 dpdklab
2023-09-27 23:33 dpdklab
2023-09-27 23:33 dpdklab
2023-09-27 23:33 dpdklab
2023-09-27 23:33 dpdklab
2023-09-27 23:32 dpdklab
2023-09-27 23:32 dpdklab
2023-09-27 23:31 dpdklab
2023-09-27 23:30 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=6514bf62.170a0220.e5ac8.4c05SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=qi.z.zhang@intel.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).