From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124889 [PATCH] doc: deprecation notice to remove LiquidIO ethdev driver
Date: Sun, 12 Mar 2023 21:44:29 +0000 (UTC) [thread overview]
Message-ID: <20230312214429.5F0326011D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/124889
_Testing PASS_
Submitter: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Date: Thursday, March 09 2023 07:07:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b15d75b2872efce397d827dac78692a919358302
124889 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Ubuntu 20.04 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| RHEL 7 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
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
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 11.3.1-2
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
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/25656/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-12 21:44 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 21:44 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-12 20:01 dpdklab
2023-03-12 10:41 dpdklab
2023-03-12 10:41 dpdklab
2023-03-12 10:39 dpdklab
2023-03-12 10:32 dpdklab
2023-03-12 10:24 dpdklab
2023-03-12 10:10 dpdklab
2023-03-12 10:02 dpdklab
2023-03-12 10:01 dpdklab
2023-03-12 9:55 dpdklab
2023-03-12 9:47 dpdklab
2023-03-12 9:47 dpdklab
2023-03-12 9:45 dpdklab
2023-03-12 9:45 dpdklab
2023-03-12 9:32 dpdklab
2023-03-12 9:30 dpdklab
2023-03-12 9:23 dpdklab
2023-03-12 9:12 dpdklab
2023-03-12 9:09 dpdklab
2023-03-12 9:08 dpdklab
2023-03-12 9:07 dpdklab
2023-03-12 9:07 dpdklab
2023-03-12 9:04 dpdklab
2023-03-12 9:01 dpdklab
2023-03-12 9:01 dpdklab
2023-03-12 8:59 dpdklab
2023-03-12 8:57 dpdklab
2023-03-12 8:54 dpdklab
2023-03-12 8:42 dpdklab
2023-03-11 21:23 dpdklab
2023-03-11 21:20 dpdklab
2023-03-11 21:03 dpdklab
2023-03-11 19:53 dpdklab
2023-03-11 3:11 dpdklab
2023-03-11 3:03 dpdklab
2023-03-11 3:02 dpdklab
2023-03-11 2:59 dpdklab
2023-03-11 2:53 dpdklab
2023-03-11 2:50 dpdklab
2023-03-11 2:50 dpdklab
2023-03-11 2:50 dpdklab
2023-03-11 2:47 dpdklab
2023-03-11 2:45 dpdklab
2023-03-11 2:43 dpdklab
2023-03-11 2:40 dpdklab
2023-03-11 2:37 dpdklab
2023-03-11 2:37 dpdklab
2023-03-11 2:34 dpdklab
2023-03-11 2:32 dpdklab
2023-03-11 2:29 dpdklab
2023-03-11 2:28 dpdklab
2023-03-11 2:25 dpdklab
2023-03-11 2:24 dpdklab
2023-03-11 2:23 dpdklab
2023-03-11 2:23 dpdklab
2023-03-11 2:18 dpdklab
2023-03-11 2:17 dpdklab
2023-03-11 2:12 dpdklab
2023-03-11 2:12 dpdklab
2023-03-11 2:08 dpdklab
2023-03-11 2:06 dpdklab
[not found] <20230309070733.537242-1-jerinj@marvell.com>
2023-03-09 6:56 ` qemudev
2023-03-09 7:00 ` qemudev
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=20230312214429.5F0326011D@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).