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] 76fa3327719b10bdb96beb2f4ac3be6c1227d2d4
Date: Fri, 29 Sep 2023 12:49:29 -0700 (PDT) [thread overview]
Message-ID: <65172a49.a70a0220.6f209.4fd3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
76fa3327719b10bdb96beb2f4ac3be6c1227d2d4 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
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/26308/
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-29 19:49 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 19:49 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-29 22:41 dpdklab
2023-09-29 21:06 dpdklab
2023-09-29 21:06 dpdklab
2023-09-29 20:40 dpdklab
2023-09-29 20:40 dpdklab
2023-09-29 20:31 dpdklab
2023-09-29 20:25 dpdklab
2023-09-29 20:25 dpdklab
2023-09-29 20:25 dpdklab
2023-09-29 20:25 dpdklab
2023-09-29 20:24 dpdklab
2023-09-29 20:24 dpdklab
2023-09-29 20:23 dpdklab
2023-09-29 20:23 dpdklab
2023-09-29 20:22 dpdklab
2023-09-29 20:21 dpdklab
2023-09-29 20:16 dpdklab
2023-09-29 20:15 dpdklab
2023-09-29 20:11 dpdklab
2023-09-29 20:09 dpdklab
2023-09-29 20:08 dpdklab
2023-09-29 20:07 dpdklab
2023-09-29 19:57 dpdklab
2023-09-29 19:57 dpdklab
2023-09-29 19:55 dpdklab
2023-09-29 19:55 dpdklab
2023-09-29 19:54 dpdklab
2023-09-29 19:53 dpdklab
2023-09-29 19:50 dpdklab
2023-09-29 19:49 dpdklab
2023-09-29 19:39 dpdklab
2023-09-29 19:39 dpdklab
2023-09-29 19:38 dpdklab
2023-09-29 19:38 dpdklab
2023-09-29 19:37 dpdklab
2023-09-29 19:36 dpdklab
2023-09-29 19:31 dpdklab
2023-09-29 19:29 dpdklab
2023-09-29 19:29 dpdklab
2023-09-29 19:10 dpdklab
2023-09-29 19:10 dpdklab
2023-09-29 19:08 dpdklab
2023-09-29 19:08 dpdklab
2023-09-29 19:08 dpdklab
2023-09-29 19:04 dpdklab
2023-09-29 19:04 dpdklab
2023-09-29 19:03 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=65172a49.a70a0220.6f209.4fd3SMTPIN_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).