From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136337-136338 [PATCH] [v6,2/2] net/octeon_ep: add Rx NEO
Date: Fri, 02 Feb 2024 08:17:23 -0800 (PST) [thread overview]
Message-ID: <65bd1593.250a0220.76f1.71afSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136338
_Testing PASS_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Friday, February 02 2024 15:09:26
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ee470dfc8a734728602a60fcc6116ab59165f10e
136337-136338 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
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 Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29042/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-02 16:17 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 16:17 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-02 21:50 dpdklab
2024-02-02 21:15 dpdklab
2024-02-02 17:02 dpdklab
2024-02-02 17:00 dpdklab
2024-02-02 16:47 dpdklab
2024-02-02 16:46 dpdklab
2024-02-02 16:30 dpdklab
2024-02-02 16:30 dpdklab
2024-02-02 16:26 dpdklab
2024-02-02 16:26 dpdklab
2024-02-02 16:25 dpdklab
2024-02-02 16:20 dpdklab
2024-02-02 16:17 dpdklab
2024-02-02 16:16 dpdklab
2024-02-02 16:14 dpdklab
2024-02-02 16:14 dpdklab
2024-02-02 16:13 dpdklab
2024-02-02 16:12 dpdklab
2024-02-02 16:11 dpdklab
2024-02-02 16:09 dpdklab
2024-02-02 16:07 dpdklab
2024-02-02 16:06 dpdklab
2024-02-02 16:05 dpdklab
2024-02-02 16:04 dpdklab
2024-02-02 16:03 dpdklab
2024-02-02 16:00 dpdklab
2024-02-02 16:00 dpdklab
2024-02-02 15:59 dpdklab
2024-02-02 15:58 dpdklab
2024-02-02 15:58 dpdklab
2024-02-02 15:58 dpdklab
2024-02-02 15:58 dpdklab
2024-02-02 15:55 dpdklab
2024-02-02 15:55 dpdklab
2024-02-02 15:55 dpdklab
2024-02-02 15:55 dpdklab
2024-02-02 15:54 dpdklab
2024-02-02 15:53 dpdklab
2024-02-02 15:53 dpdklab
2024-02-02 15:53 dpdklab
2024-02-02 15:52 dpdklab
2024-02-02 15:51 dpdklab
2024-02-02 15:51 dpdklab
2024-02-02 15:49 dpdklab
2024-02-02 15:49 dpdklab
2024-02-02 15:48 dpdklab
2024-02-02 15:48 dpdklab
2024-02-02 15:48 dpdklab
2024-02-02 15:47 dpdklab
2024-02-02 15:46 dpdklab
2024-02-02 15:45 dpdklab
2024-02-02 15:45 dpdklab
2024-02-02 15:44 dpdklab
2024-02-02 15:44 dpdklab
2024-02-02 15:44 dpdklab
2024-02-02 15:44 dpdklab
2024-02-02 15:44 dpdklab
2024-02-02 15:43 dpdklab
2024-02-02 15:43 dpdklab
2024-02-02 15:42 dpdklab
2024-02-02 15:42 dpdklab
2024-02-02 15:41 dpdklab
2024-02-02 15:41 dpdklab
2024-02-02 15:41 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=65bd1593.250a0220.76f1.71afSMTPIN_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).