From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Subject: |SUCCESS| pw135020-135022 [PATCH] [v2,3/3] event/cnxk: add option to
Date: Mon, 11 Dec 2023 06:12:31 -0800 (PST) [thread overview]
Message-ID: <657718cf.050a0220.16a2c.137dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135022
_Testing PASS_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Monday, December 11 2023 13:23:20
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f2d5afbb2c05d7647da7ea914887c52115652651
135020-135022 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Debian Buster | 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
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28583/
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-11 14:12 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 14:12 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-11 15:41 dpdklab
2023-12-11 15:39 dpdklab
2023-12-11 14:59 dpdklab
2023-12-11 14:56 dpdklab
2023-12-11 14:55 dpdklab
2023-12-11 14:55 dpdklab
2023-12-11 14:53 dpdklab
2023-12-11 14:53 dpdklab
2023-12-11 14:51 dpdklab
2023-12-11 14:51 dpdklab
2023-12-11 14:51 dpdklab
2023-12-11 14:48 dpdklab
2023-12-11 14:48 dpdklab
2023-12-11 14:47 dpdklab
2023-12-11 14:47 dpdklab
2023-12-11 14:47 dpdklab
2023-12-11 14:43 dpdklab
2023-12-11 14:43 dpdklab
2023-12-11 14:42 dpdklab
2023-12-11 14:41 dpdklab
2023-12-11 14:40 dpdklab
2023-12-11 14:40 dpdklab
2023-12-11 14:40 dpdklab
2023-12-11 14:40 dpdklab
2023-12-11 14:37 dpdklab
2023-12-11 14:36 dpdklab
2023-12-11 14:36 dpdklab
2023-12-11 14:35 dpdklab
2023-12-11 14:35 dpdklab
2023-12-11 14:33 dpdklab
2023-12-11 14:33 dpdklab
2023-12-11 14:24 dpdklab
2023-12-11 14:23 dpdklab
2023-12-11 14:22 dpdklab
2023-12-11 14:22 dpdklab
2023-12-11 14:20 dpdklab
2023-12-11 14:20 dpdklab
2023-12-11 14:20 dpdklab
2023-12-11 14:20 dpdklab
2023-12-11 14:20 dpdklab
2023-12-11 14:19 dpdklab
2023-12-11 14:19 dpdklab
2023-12-11 14:18 dpdklab
2023-12-11 14:18 dpdklab
2023-12-11 14:16 dpdklab
2023-12-11 14:16 dpdklab
2023-12-11 14:15 dpdklab
2023-12-11 14:15 dpdklab
2023-12-11 14:14 dpdklab
2023-12-11 14:14 dpdklab
2023-12-11 14:14 dpdklab
2023-12-11 14:13 dpdklab
2023-12-11 14:13 dpdklab
2023-12-11 14:13 dpdklab
2023-12-11 14:12 dpdklab
2023-12-11 14:12 dpdklab
2023-12-11 14:12 dpdklab
2023-12-11 14:11 dpdklab
2023-12-11 14:11 dpdklab
2023-12-11 14:08 dpdklab
2023-12-11 14:07 dpdklab
2023-12-11 14:07 dpdklab
2023-12-11 14:07 dpdklab
2023-12-11 13:59 dpdklab
2023-12-11 13:59 dpdklab
2023-12-11 13:58 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=657718cf.050a0220.16a2c.137dSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=pbhagavatula@marvell.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).