From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Chaoyong He <chaoyong.he@corigine.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| pw133551-133553 [PATCH] [3/3] net/nfp: fix the reconfigure
Date: Sat, 28 Oct 2023 02:02:05 -0700 (PDT) [thread overview]
Message-ID: <653cce0d.170a0220.bc6f6.85ceSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133553
_Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Saturday, October 28 2023 06:23:15
DPDK git baseline: Repo:dpdk-next-net
Branch: master
CommitID:1564a4b7e5632749fcc592254b69f9de11e06b94
133551-133553 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28124/
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-28 9:02 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 9:02 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-28 10:08 dpdklab
2023-10-28 9:35 dpdklab
2023-10-28 9:25 dpdklab
2023-10-28 9:14 dpdklab
2023-10-28 9:13 dpdklab
2023-10-28 9:12 dpdklab
2023-10-28 9:11 dpdklab
2023-10-28 9:11 dpdklab
2023-10-28 9:10 dpdklab
2023-10-28 9:09 dpdklab
2023-10-28 9:07 dpdklab
2023-10-28 9:05 dpdklab
2023-10-28 9:05 dpdklab
2023-10-28 9:04 dpdklab
2023-10-28 9:03 dpdklab
2023-10-28 9:02 dpdklab
2023-10-28 9:01 dpdklab
2023-10-28 9:01 dpdklab
2023-10-28 8:56 dpdklab
2023-10-28 8:56 dpdklab
2023-10-28 8:55 dpdklab
2023-10-28 8:54 dpdklab
2023-10-28 8:54 dpdklab
2023-10-28 8:54 dpdklab
2023-10-28 8:54 dpdklab
2023-10-28 8:54 dpdklab
2023-10-28 8:53 dpdklab
2023-10-28 8:53 dpdklab
2023-10-28 8:53 dpdklab
2023-10-28 8:53 dpdklab
2023-10-28 8:52 dpdklab
2023-10-28 8:52 dpdklab
2023-10-28 8:52 dpdklab
2023-10-28 8:51 dpdklab
2023-10-28 8:51 dpdklab
2023-10-28 8:51 dpdklab
2023-10-28 8:51 dpdklab
2023-10-28 8:51 dpdklab
2023-10-28 8:51 dpdklab
2023-10-28 8:50 dpdklab
2023-10-28 8:50 dpdklab
2023-10-28 8:50 dpdklab
2023-10-28 8:50 dpdklab
2023-10-28 8:49 dpdklab
2023-10-28 8:48 dpdklab
2023-10-28 8:48 dpdklab
2023-10-28 8:46 dpdklab
2023-10-28 8:46 dpdklab
2023-10-28 8:45 dpdklab
2023-10-28 8:44 dpdklab
2023-10-28 8:30 dpdklab
2023-10-28 8:29 dpdklab
2023-10-28 8:28 dpdklab
2023-10-28 8:13 dpdklab
2023-10-28 8:12 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=653cce0d.170a0220.bc6f6.85ceSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=chaoyong.he@corigine.com \
--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).