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| pw125057-125058 [PATCH] [2/2] common/cnxk: fix SPI to SA index destroy
Date: Tue, 14 Mar 2023 16:53:45 +0000 (UTC) [thread overview]
Message-ID: <20230314165345.4C8A26011D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/125058
_Testing PASS_
Submitter: Satheesh Paul Antonysamy <psatheesh@marvell.com>
Date: Monday, March 13 2023 05:24:03
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:baf13c3135d0c5998fff7edc23fb89412dc89246
125057-125058 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| CentOS Stream 9 | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| RHEL 7 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| Ubuntu 20.04 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 11.3.1-2
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)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25700/
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-14 16:53 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 16:53 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-14 15:30 dpdklab
2023-03-13 20:56 dpdklab
2023-03-13 20:55 dpdklab
2023-03-13 20:21 dpdklab
2023-03-13 20:19 dpdklab
2023-03-13 20:15 dpdklab
2023-03-13 20:14 dpdklab
2023-03-13 20:12 dpdklab
2023-03-13 20:11 dpdklab
2023-03-13 20:06 dpdklab
2023-03-13 20:00 dpdklab
2023-03-13 19:53 dpdklab
2023-03-13 19:46 dpdklab
2023-03-13 19:45 dpdklab
2023-03-13 19:45 dpdklab
2023-03-13 19:34 dpdklab
2023-03-13 19:33 dpdklab
2023-03-13 18:58 dpdklab
2023-03-13 18:57 dpdklab
2023-03-13 18:56 dpdklab
2023-03-13 18:54 dpdklab
2023-03-13 18:52 dpdklab
2023-03-13 18:49 dpdklab
2023-03-13 18:49 dpdklab
2023-03-13 18:36 dpdklab
2023-03-13 18:20 dpdklab
2023-03-13 18:12 dpdklab
2023-03-13 17:58 dpdklab
2023-03-13 10:31 dpdklab
2023-03-13 9:38 dpdklab
2023-03-13 8:19 dpdklab
2023-03-13 8:03 dpdklab
2023-03-13 7:16 dpdklab
2023-03-13 7:12 dpdklab
2023-03-13 7:10 dpdklab
2023-03-13 7:05 dpdklab
2023-03-13 7:04 dpdklab
2023-03-13 7:04 dpdklab
2023-03-13 7:00 dpdklab
2023-03-13 6:58 dpdklab
2023-03-13 6:57 dpdklab
2023-03-13 6:56 dpdklab
2023-03-13 6:56 dpdklab
2023-03-13 6:50 dpdklab
2023-03-13 6:44 dpdklab
2023-03-13 6:44 dpdklab
2023-03-13 6:40 dpdklab
2023-03-13 6:35 dpdklab
2023-03-13 6:34 dpdklab
2023-03-13 6:31 dpdklab
2023-03-13 6:30 dpdklab
2023-03-13 6:27 dpdklab
2023-03-13 6:25 dpdklab
2023-03-13 6:19 dpdklab
2023-03-13 6:15 dpdklab
2023-03-13 6:13 dpdklab
[not found] <20230313052403.230953-2-psatheesh@marvell.com>
2023-03-13 5:13 ` |SUCCESS| pw125057-125058 [PATCH 2/2] " qemudev
2023-03-13 5:16 ` 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=20230314165345.4C8A26011D@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).