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] 40435075a790fac6e5d5ad7a967950f5e56e45c8
Date: Thu, 05 Oct 2023 11:27:14 -0700 (PDT) [thread overview]
Message-ID: <651f0002.250a0220.e3c02.7399SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
40435075a790fac6e5d5ad7a967950f5e56e45c8 --> testing pass
Test environment and result as below:
+---------------------+--------------------+
| Environment | dpdk_meson_compile |
+=====================+====================+
| FreeBSD 13 | PASS |
+---------------------+--------------------+
| CentOS Stream 9 | PASS |
+---------------------+--------------------+
| CentOS Stream 8 | PASS |
+---------------------+--------------------+
| Fedora 37 | PASS |
+---------------------+--------------------+
| Windows Server 2019 | PASS |
+---------------------+--------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
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/26365/
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 18:27 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 18:27 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-05 19:46 dpdklab
2023-10-05 19:42 dpdklab
2023-10-05 19:28 dpdklab
2023-10-05 19:27 dpdklab
2023-10-05 19:21 dpdklab
2023-10-05 19:20 dpdklab
2023-10-05 19:20 dpdklab
2023-10-05 19:20 dpdklab
2023-10-05 19:19 dpdklab
2023-10-05 19:16 dpdklab
2023-10-05 19:15 dpdklab
2023-10-05 19:12 dpdklab
2023-10-05 19:07 dpdklab
2023-10-05 19:05 dpdklab
2023-10-05 19:01 dpdklab
2023-10-05 18:57 dpdklab
2023-10-05 18:53 dpdklab
2023-10-05 18:48 dpdklab
2023-10-05 18:44 dpdklab
2023-10-05 18:44 dpdklab
2023-10-05 18:41 dpdklab
2023-10-05 18:41 dpdklab
2023-10-05 18:39 dpdklab
2023-10-05 18:39 dpdklab
2023-10-05 18:39 dpdklab
2023-10-05 18:36 dpdklab
2023-10-05 18:36 dpdklab
2023-10-05 18:36 dpdklab
2023-10-05 18:35 dpdklab
2023-10-05 18:34 dpdklab
2023-10-05 18:34 dpdklab
2023-10-05 18:32 dpdklab
2023-10-05 18:32 dpdklab
2023-10-05 18:31 dpdklab
2023-10-05 18:30 dpdklab
2023-10-05 18:30 dpdklab
2023-10-05 18:30 dpdklab
2023-10-05 18:29 dpdklab
2023-10-05 18:28 dpdklab
2023-10-05 18:27 dpdklab
2023-10-05 18:26 dpdklab
2023-10-05 18:26 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=651f0002.250a0220.e3c02.7399SMTPIN_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).