From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130653 [PATCH] test/security: fix buffer leaks in error
Date: Tue, 22 Aug 2023 19:46:02 -0700 (PDT) [thread overview]
Message-ID: <64e572ea.6b0a0220.f03c1.aa9aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130653
_Testing PASS_
Submitter: Akhil Goyal <gakhil@marvell.com>
Date: Tuesday, August 22 2023 17:33:16
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:971d2b57972919527e27ed683032a71864a2eb56
130653 --> testing pass
Test environment and result as below:
+-----------------+----------------+
| Environment | dpdk_unit_test |
+=================+================+
| CentOS Stream 8 | PASS |
+-----------------+----------------+
| CentOS Stream 9 | PASS |
+-----------------+----------------+
| Debian Buster | PASS |
+-----------------+----------------+
| Debian Bullseye | PASS |
+-----------------+----------------+
| Fedora 38 | PASS |
+-----------------+----------------+
| Fedora 37 | 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
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
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/27422/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-23 2:46 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 2:46 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-23 17:12 dpdklab
2023-08-23 17:08 dpdklab
2023-08-23 16:51 dpdklab
2023-08-23 16:45 dpdklab
2023-08-23 16:41 dpdklab
2023-08-23 9:11 dpdklab
2023-08-23 4:22 dpdklab
2023-08-23 2:51 dpdklab
2023-08-23 2:51 dpdklab
2023-08-23 2:49 dpdklab
2023-08-23 2:47 dpdklab
2023-08-23 2:43 dpdklab
2023-08-23 2:40 dpdklab
2023-08-23 2:36 dpdklab
2023-08-23 2:35 dpdklab
2023-08-23 2:32 dpdklab
2023-08-23 2:29 dpdklab
2023-08-23 2:29 dpdklab
2023-08-23 2:25 dpdklab
2023-08-23 2:22 dpdklab
2023-08-23 2:21 dpdklab
2023-08-23 2:18 dpdklab
2023-08-23 2:14 dpdklab
2023-08-23 2:07 dpdklab
2023-08-23 2:06 dpdklab
2023-08-23 2:05 dpdklab
2023-08-23 2:03 dpdklab
2023-08-23 2:02 dpdklab
2023-08-23 1:52 dpdklab
2023-08-23 1:51 dpdklab
2023-08-23 1:42 dpdklab
2023-08-23 1:18 dpdklab
2023-08-23 1:17 dpdklab
2023-08-23 1:13 dpdklab
2023-08-23 1:12 dpdklab
2023-08-23 1:12 dpdklab
2023-08-23 1:11 dpdklab
2023-08-23 1:09 dpdklab
2023-08-23 1:09 dpdklab
2023-08-23 1:08 dpdklab
2023-08-23 1:08 dpdklab
2023-08-23 1:08 dpdklab
2023-08-23 1:07 dpdklab
2023-08-23 1:07 dpdklab
2023-08-23 1:07 dpdklab
2023-08-23 1:06 dpdklab
2023-08-23 1:05 dpdklab
2023-08-23 1:05 dpdklab
2023-08-23 1:04 dpdklab
2023-08-23 1:03 dpdklab
2023-08-23 1:03 dpdklab
2023-08-23 1:02 dpdklab
2023-08-23 0:56 dpdklab
2023-08-23 0:54 dpdklab
2023-08-23 0:34 dpdklab
2023-08-22 23:33 dpdklab
2023-08-22 23:17 dpdklab
2023-08-22 23:16 dpdklab
2023-08-22 23:09 dpdklab
2023-08-22 23:06 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=64e572ea.6b0a0220.f03c1.aa9aSMTPIN_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).