From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136293 [PATCH] [v4] event/cnxk: use WFE LDP loop for get
Date: Thu, 01 Feb 2024 19:37:14 -0800 (PST) [thread overview]
Message-ID: <65bc636a.170a0220.a07be.1f08SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136293
_Testing PASS_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Thursday, February 01 2024 22:03:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:82b8ea38ecf2a24fa7bd257a007a2d8351e6e5ad
136293 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| CentOS Stream 9 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| Fedora 38 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| Fedora 37 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
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
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29024/
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 3:37 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 3:37 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-02 6:19 dpdklab
2024-02-02 5:42 dpdklab
2024-02-02 5:39 dpdklab
2024-02-02 5:36 dpdklab
2024-02-02 5:01 dpdklab
2024-02-02 4:57 dpdklab
2024-02-02 4:47 dpdklab
2024-02-02 4:46 dpdklab
2024-02-02 4:45 dpdklab
2024-02-02 4:43 dpdklab
2024-02-02 4:43 dpdklab
2024-02-02 4:41 dpdklab
2024-02-02 4:37 dpdklab
2024-02-02 4:36 dpdklab
2024-02-02 4:16 dpdklab
2024-02-02 4:16 dpdklab
2024-02-02 4:16 dpdklab
2024-02-02 4:15 dpdklab
2024-02-02 4:15 dpdklab
2024-02-02 4:14 dpdklab
2024-02-02 4:13 dpdklab
2024-02-02 4:08 dpdklab
2024-02-02 4:06 dpdklab
2024-02-02 4:05 dpdklab
2024-02-02 4:05 dpdklab
2024-02-02 4:05 dpdklab
2024-02-02 4:04 dpdklab
2024-02-02 4:04 dpdklab
2024-02-02 4:03 dpdklab
2024-02-02 3:56 dpdklab
2024-02-02 3:55 dpdklab
2024-02-02 3:55 dpdklab
2024-02-02 3:52 dpdklab
2024-02-02 3:52 dpdklab
2024-02-02 3:52 dpdklab
2024-02-02 3:49 dpdklab
2024-02-02 3:46 dpdklab
2024-02-02 3:46 dpdklab
2024-02-02 3:45 dpdklab
2024-02-02 3:45 dpdklab
2024-02-02 3:45 dpdklab
2024-02-02 3:45 dpdklab
2024-02-02 3:44 dpdklab
2024-02-02 3:44 dpdklab
2024-02-02 3:43 dpdklab
2024-02-02 3:43 dpdklab
2024-02-02 3:41 dpdklab
2024-02-02 3:40 dpdklab
2024-02-02 3:36 dpdklab
2024-02-02 3:35 dpdklab
2024-02-02 3:35 dpdklab
2024-02-02 3:31 dpdklab
2024-02-02 3:30 dpdklab
2024-02-02 3:30 dpdklab
2024-02-02 3:29 dpdklab
2024-02-02 3:26 dpdklab
2024-02-02 3:26 dpdklab
2024-02-02 3:10 dpdklab
2024-02-02 3:09 dpdklab
2024-02-02 2:59 dpdklab
2024-02-02 2:59 dpdklab
2024-02-02 2:58 dpdklab
2024-02-02 2:56 dpdklab
2024-02-02 2:55 dpdklab
2024-02-02 2:55 dpdklab
2024-02-02 2:53 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=65bc636a.170a0220.a07be.1f08SMTPIN_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).