From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135222 [PATCH] net/cnxk: fix issue with RSS configuratio
Date: Fri, 15 Dec 2023 01:13:51 -0800 (PST) [thread overview]
Message-ID: <657c18cf.170a0220.2b5c9.bd8eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135222
_Testing PASS_
Submitter: Satheesh Paul Antonysamy <psatheesh@marvell.com>
Date: Friday, December 15 2023 06:45:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
135222 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | 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
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28643/
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-15 9:13 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 9:13 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-15 17:42 dpdklab
2023-12-15 10:29 dpdklab
2023-12-15 10:27 dpdklab
2023-12-15 10:19 dpdklab
2023-12-15 10:17 dpdklab
2023-12-15 10:16 dpdklab
2023-12-15 10:12 dpdklab
2023-12-15 10:04 dpdklab
2023-12-15 10:02 dpdklab
2023-12-15 10:00 dpdklab
2023-12-15 9:57 dpdklab
2023-12-15 9:56 dpdklab
2023-12-15 9:56 dpdklab
2023-12-15 9:54 dpdklab
2023-12-15 9:52 dpdklab
2023-12-15 9:51 dpdklab
2023-12-15 9:36 dpdklab
2023-12-15 9:33 dpdklab
2023-12-15 9:32 dpdklab
2023-12-15 9:31 dpdklab
2023-12-15 9:27 dpdklab
2023-12-15 9:25 dpdklab
2023-12-15 9:24 dpdklab
2023-12-15 9:24 dpdklab
2023-12-15 9:23 dpdklab
2023-12-15 9:20 dpdklab
2023-12-15 9:20 dpdklab
2023-12-15 9:17 dpdklab
2023-12-15 9:16 dpdklab
2023-12-15 9:16 dpdklab
2023-12-15 9:14 dpdklab
2023-12-15 9:12 dpdklab
2023-12-15 9:10 dpdklab
2023-12-15 9:09 dpdklab
2023-12-15 9:06 dpdklab
2023-12-15 9:05 dpdklab
2023-12-15 9:01 dpdklab
2023-12-15 9:01 dpdklab
2023-12-15 9:00 dpdklab
2023-12-15 8:59 dpdklab
2023-12-15 8:58 dpdklab
2023-12-15 8:56 dpdklab
2023-12-15 8:56 dpdklab
2023-12-15 8:31 dpdklab
2023-12-15 8:29 dpdklab
2023-12-15 8:24 dpdklab
2023-12-15 8:14 dpdklab
2023-12-15 8:13 dpdklab
2023-12-15 8:13 dpdklab
2023-12-15 8:13 dpdklab
2023-12-15 8:12 dpdklab
2023-12-15 8:09 dpdklab
2023-12-15 8:07 dpdklab
2023-12-15 8:05 dpdklab
2023-12-15 8:04 dpdklab
2023-12-15 8:04 dpdklab
2023-12-15 8:04 dpdklab
2023-12-15 8:03 dpdklab
2023-12-15 8:02 dpdklab
2023-12-15 7:58 dpdklab
2023-12-15 7:57 dpdklab
2023-12-15 7:57 dpdklab
2023-12-15 7:57 dpdklab
2023-12-15 7:57 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=657c18cf.170a0220.2b5c9.bd8eSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).