From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135734 [PATCH] event/cnxk: use WFE LDP loop for getwork
Date: Thu, 04 Jan 2024 13:03:28 -0800 (PST) [thread overview]
Message-ID: <65971d20.050a0220.aec0b.1544SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135734
_Testing PASS_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Thursday, January 04 2024 19:36:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871
135734 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Fedora 37 | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| Fedora 38 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
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
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/28793/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-04 21:03 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 21:03 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-05 7:23 dpdklab
2024-01-05 7:15 dpdklab
2024-01-04 22:41 dpdklab
2024-01-04 22:18 dpdklab
2024-01-04 21:46 dpdklab
2024-01-04 21:27 dpdklab
2024-01-04 21:05 dpdklab
2024-01-04 21:05 dpdklab
2024-01-04 21:04 dpdklab
2024-01-04 21:04 dpdklab
2024-01-04 21:04 dpdklab
2024-01-04 21:03 dpdklab
2024-01-04 21:01 dpdklab
2024-01-04 21:01 dpdklab
2024-01-04 21:00 dpdklab
2024-01-04 20:59 dpdklab
2024-01-04 20:58 dpdklab
2024-01-04 20:58 dpdklab
2024-01-04 20:57 dpdklab
2024-01-04 20:56 dpdklab
2024-01-04 20:55 dpdklab
2024-01-04 20:55 dpdklab
2024-01-04 20:54 dpdklab
2024-01-04 20:53 dpdklab
2024-01-04 20:52 dpdklab
2024-01-04 20:52 dpdklab
2024-01-04 20:51 dpdklab
2024-01-04 20:50 dpdklab
2024-01-04 20:50 dpdklab
2024-01-04 20:50 dpdklab
2024-01-04 20:49 dpdklab
2024-01-04 20:49 dpdklab
2024-01-04 20:48 dpdklab
2024-01-04 20:48 dpdklab
2024-01-04 20:47 dpdklab
2024-01-04 20:47 dpdklab
2024-01-04 20:46 dpdklab
2024-01-04 20:46 dpdklab
2024-01-04 20:44 dpdklab
2024-01-04 20:42 dpdklab
2024-01-04 20:42 dpdklab
2024-01-04 20:41 dpdklab
2024-01-04 20:41 dpdklab
2024-01-04 20:40 dpdklab
2024-01-04 20:40 dpdklab
2024-01-04 20:39 dpdklab
2024-01-04 20:39 dpdklab
2024-01-04 20:38 dpdklab
2024-01-04 20:38 dpdklab
2024-01-04 20:37 dpdklab
2024-01-04 20:37 dpdklab
2024-01-04 20:36 dpdklab
2024-01-04 20:35 dpdklab
2024-01-04 20:35 dpdklab
2024-01-04 20:35 dpdklab
2024-01-04 20:34 dpdklab
2024-01-04 20:34 dpdklab
2024-01-04 20:33 dpdklab
2024-01-04 20:32 dpdklab
2024-01-04 20:19 dpdklab
2024-01-04 20:18 dpdklab
2024-01-04 20:17 dpdklab
2024-01-04 20:16 dpdklab
2024-01-04 20:15 dpdklab
2024-01-04 20:15 dpdklab
2024-01-04 20:14 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=65971d20.050a0220.aec0b.1544SMTPIN_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).