From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Power@dpdk.org, Ciara <ciara.power@intel.com>
Subject: |SUCCESS| pw134160 [PATCH] [v3] crypto/openssl: fix asym memory leak
Date: Mon, 13 Nov 2023 09:56:46 -0800 (PST) [thread overview]
Message-ID: <6552635e.2e0a0220.35874.41c4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/134160
_Testing PASS_
Submitter: Power, Ciara <ciara.power@intel.com>
Date: Monday, November 13 2023 13:16:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d677a3eb1b4e2d38c193fabd755dac30ee04c2df
134160 --> testing pass
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| CentOS Stream 8 | PASS |
+------------------+----------------+
| CentOS Stream 9 | PASS |
+------------------+----------------+
| Debian Buster | PASS |
+------------------+----------------+
| Fedora 37 | PASS |
+------------------+----------------+
| Fedora 38 | PASS |
+------------------+----------------+
| openSUSE Leap 15 | PASS |
+------------------+----------------+
| RHEL8 | PASS |
+------------------+----------------+
| Ubuntu 20.04 | PASS |
+------------------+----------------+
| Ubuntu 22.04 | PASS |
+------------------+----------------+
| Debian Bullseye | PASS |
+------------------+----------------+
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 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
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
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)
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28354/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-13 17:57 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 17:56 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-15 18:03 dpdklab
2023-11-15 17:43 dpdklab
2023-11-13 20:57 dpdklab
2023-11-13 19:02 dpdklab
2023-11-13 17:56 dpdklab
2023-11-13 17:56 dpdklab
2023-11-13 17:56 dpdklab
2023-11-13 17:55 dpdklab
2023-11-13 17:55 dpdklab
2023-11-13 17:55 dpdklab
2023-11-13 17:55 dpdklab
2023-11-13 17:55 dpdklab
2023-11-13 17:55 dpdklab
2023-11-13 17:54 dpdklab
2023-11-13 17:54 dpdklab
2023-11-13 17:54 dpdklab
2023-11-13 17:54 dpdklab
2023-11-13 17:54 dpdklab
2023-11-13 17:54 dpdklab
2023-11-13 17:54 dpdklab
2023-11-13 17:54 dpdklab
2023-11-13 17:54 dpdklab
2023-11-13 17:54 dpdklab
2023-11-13 17:54 dpdklab
2023-11-13 17:54 dpdklab
2023-11-13 17:53 dpdklab
2023-11-13 17:51 dpdklab
2023-11-13 17:49 dpdklab
2023-11-13 17:49 dpdklab
2023-11-13 17:48 dpdklab
2023-11-13 17:48 dpdklab
2023-11-13 17:48 dpdklab
2023-11-13 17:48 dpdklab
2023-11-13 17:48 dpdklab
2023-11-13 17:47 dpdklab
2023-11-13 17:47 dpdklab
2023-11-13 17:47 dpdklab
2023-11-13 17:46 dpdklab
2023-11-13 17:46 dpdklab
2023-11-13 17:45 dpdklab
2023-11-13 17:45 dpdklab
2023-11-13 17:45 dpdklab
2023-11-13 17:45 dpdklab
2023-11-13 17:45 dpdklab
2023-11-13 17:28 dpdklab
2023-11-13 17:25 dpdklab
2023-11-13 17:23 dpdklab
2023-11-13 17:23 dpdklab
2023-11-13 17:22 dpdklab
2023-11-13 17:18 dpdklab
2023-11-13 17:11 dpdklab
2023-11-13 17:11 dpdklab
2023-11-13 17:10 dpdklab
2023-11-13 17:10 dpdklab
2023-11-13 16: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=6552635e.2e0a0220.35874.41c4SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=Power@dpdk.org \
--cc=ciara.power@intel.com \
--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).