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| pw135556-135569 [PATCH] [v5,14/14] net/nfp: support offloa
Date: Mon, 25 Dec 2023 19:54:34 -0800 (PST) [thread overview]
Message-ID: <658a4e7a.d40a0220.a59b1.de2eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135569
_Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Tuesday, December 26 2023 02:37:45
DPDK git baseline: Repo:dpdk-next-net
Branch: master
CommitID:84bfce561f24a33cb186efdc1cf8dc4a8c96fd26
135556-135569 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
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/patchsets/28736/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-26 3:54 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 3:54 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-26 4:32 dpdklab
2023-12-26 4:31 dpdklab
2023-12-26 4:30 dpdklab
2023-12-26 4:29 dpdklab
2023-12-26 4:29 dpdklab
2023-12-26 4:27 dpdklab
2023-12-26 4:26 dpdklab
2023-12-26 4:24 dpdklab
2023-12-26 4:23 dpdklab
2023-12-26 4:21 dpdklab
2023-12-26 4:17 dpdklab
2023-12-26 4:13 dpdklab
2023-12-26 4:13 dpdklab
2023-12-26 4:06 dpdklab
2023-12-26 4:05 dpdklab
2023-12-26 4:04 dpdklab
2023-12-26 4:00 dpdklab
2023-12-26 4:00 dpdklab
2023-12-26 4:00 dpdklab
2023-12-26 3:58 dpdklab
2023-12-26 3:58 dpdklab
2023-12-26 3:57 dpdklab
2023-12-26 3:56 dpdklab
2023-12-26 3:51 dpdklab
2023-12-26 3:50 dpdklab
2023-12-26 3:46 dpdklab
2023-12-26 3:46 dpdklab
2023-12-26 3:44 dpdklab
2023-12-26 3:44 dpdklab
2023-12-26 3:43 dpdklab
2023-12-26 3:43 dpdklab
2023-12-26 3:41 dpdklab
2023-12-26 3:39 dpdklab
2023-12-26 3:39 dpdklab
2023-12-26 3:34 dpdklab
2023-12-26 3:29 dpdklab
2023-12-26 3:29 dpdklab
2023-12-26 3:28 dpdklab
2023-12-26 3:27 dpdklab
2023-12-26 3:27 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=658a4e7a.d40a0220.a59b1.de2eSMTPIN_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).