From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw128667 [PATCH] bus/cdx: Fix resource leak
Date: Wed, 14 Jun 2023 08:45:41 -0700 (PDT) [thread overview]
Message-ID: <6489e0a5.810a0220.9bc85.3759SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/128667
_Testing PASS_
Submitter: Abhijit Gangurde <abhijit.gangurde@amd.com>
Date: Wednesday, June 14 2023 10:24:24
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:050de60d8a5cef8b7c10b4471905ca8bf69d670e
128667 --> testing pass
Test environment and result as below:
+-----------------+----------+
| Environment | abi_test |
+=================+==========+
| Fedora 38 | PASS |
+-----------------+----------+
| CentOS Stream 8 | PASS |
+-----------------+----------+
| CentOS Stream 9 | PASS |
+-----------------+----------+
| Debian Bullseye | PASS |
+-----------------+----------+
| RHEL 7 | PASS |
+-----------------+----------+
| Ubuntu 22.04 | PASS |
+-----------------+----------+
| Debian Buster | PASS |
+-----------------+----------+
| RHEL8 | PASS |
+-----------------+----------+
| Fedora 37 | PASS |
+-----------------+----------+
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
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
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)
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
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 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26681/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-14 15:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 15:45 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-15 12:02 dpdklab
2023-06-14 20:28 dpdklab
2023-06-14 20:08 dpdklab
2023-06-14 19:21 dpdklab
2023-06-14 17:57 dpdklab
2023-06-14 17:14 dpdklab
2023-06-14 17:14 dpdklab
2023-06-14 16:57 dpdklab
2023-06-14 16:27 dpdklab
2023-06-14 16:23 dpdklab
2023-06-14 16:07 dpdklab
2023-06-14 16:00 dpdklab
2023-06-14 16:00 dpdklab
2023-06-14 15:45 dpdklab
2023-06-14 15:41 dpdklab
2023-06-14 15:41 dpdklab
2023-06-14 15:36 dpdklab
2023-06-14 15:29 dpdklab
2023-06-14 15:28 dpdklab
2023-06-14 15:27 dpdklab
2023-06-14 15:08 dpdklab
2023-06-14 15:07 dpdklab
2023-06-14 14:53 dpdklab
2023-06-14 14:52 dpdklab
2023-06-14 14:50 dpdklab
2023-06-14 14:45 dpdklab
[not found] <20230614102424.224679-1-abhijit.gangurde@amd.com>
2023-06-14 10:17 ` qemudev
2023-06-14 10:21 ` qemudev
2023-06-14 10:25 ` checkpatch
2023-06-14 11:59 ` 0-day Robot
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=6489e0a5.810a0220.9bc85.3759SMTPIN_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).