From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] 6676a3793b4292baf606092a8e3e14ea67550c58
Date: Thu, 25 Jan 2024 00:46:29 -0800 (PST) [thread overview]
Message-ID: <65b21fe5.250a0220.88f2.dab1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
6676a3793b4292baf606092a8e3e14ea67550c58 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27798/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-25 8:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 8:46 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-26 18:21 dpdklab
2024-01-26 18:00 dpdklab
2024-01-26 17:52 dpdklab
2024-01-25 10:05 dpdklab
2024-01-25 9:31 dpdklab
2024-01-25 9:11 dpdklab
2024-01-25 9:06 dpdklab
2024-01-25 9:06 dpdklab
2024-01-25 9:03 dpdklab
2024-01-25 8:59 dpdklab
2024-01-25 8:58 dpdklab
2024-01-25 8:55 dpdklab
2024-01-25 8:55 dpdklab
2024-01-25 8:51 dpdklab
2024-01-25 8:48 dpdklab
2024-01-25 8:25 dpdklab
2024-01-25 8:16 dpdklab
2024-01-25 7:56 dpdklab
2024-01-25 7:53 dpdklab
2024-01-25 7:49 dpdklab
2024-01-25 7:49 dpdklab
2024-01-25 7:45 dpdklab
2024-01-25 7:45 dpdklab
2024-01-25 7:44 dpdklab
2024-01-25 7:44 dpdklab
2024-01-25 7:44 dpdklab
2024-01-25 7:42 dpdklab
2024-01-25 7:41 dpdklab
2024-01-25 7:40 dpdklab
2024-01-25 7:40 dpdklab
2024-01-25 7:39 dpdklab
2024-01-25 7:38 dpdklab
2024-01-25 7:38 dpdklab
2024-01-25 7:37 dpdklab
2024-01-25 7:37 dpdklab
2024-01-25 7:36 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=65b21fe5.250a0220.88f2.dab1SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@amd.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).