From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132689 [PATCH] net/cpfl: fix memory leak
Date: Tue, 17 Oct 2023 02:20:09 -0700 (PDT) [thread overview]
Message-ID: <652e51c9.020a0220.615c9.2d42SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132689
_Testing PASS_
Submitter: Xing, Beilei <beilei.xing@intel.com>
Date: Tuesday, October 17 2023 11:06:55
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:55bc9233a2065b3003e90710e4d139159f7c3ebf
132689 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
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
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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/27953/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-17 9:20 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 9:20 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-18 20:13 dpdklab
2023-10-17 21:49 dpdklab
2023-10-17 21:45 dpdklab
2023-10-17 10:09 dpdklab
2023-10-17 9:58 dpdklab
2023-10-17 9:49 dpdklab
2023-10-17 9:49 dpdklab
2023-10-17 9:45 dpdklab
2023-10-17 9:42 dpdklab
2023-10-17 9:42 dpdklab
2023-10-17 9:42 dpdklab
2023-10-17 9:41 dpdklab
2023-10-17 9:41 dpdklab
2023-10-17 9:41 dpdklab
2023-10-17 9:38 dpdklab
2023-10-17 9:26 dpdklab
2023-10-17 9:07 dpdklab
2023-10-17 9:07 dpdklab
2023-10-17 9:07 dpdklab
2023-10-17 9:04 dpdklab
2023-10-17 9:03 dpdklab
2023-10-17 9:03 dpdklab
2023-10-17 9:03 dpdklab
2023-10-17 9:03 dpdklab
2023-10-17 9:02 dpdklab
2023-10-17 9:01 dpdklab
2023-10-17 9:00 dpdklab
2023-10-17 9:00 dpdklab
2023-10-17 8:59 dpdklab
2023-10-17 8:58 dpdklab
2023-10-17 8:58 dpdklab
2023-10-17 8:57 dpdklab
2023-10-17 8:52 dpdklab
2023-10-17 8:51 dpdklab
2023-10-17 8:51 dpdklab
2023-10-17 8:50 dpdklab
2023-10-17 8:50 dpdklab
2023-10-17 8:42 dpdklab
2023-10-17 8:41 dpdklab
2023-10-17 8:41 dpdklab
2023-10-17 8:34 dpdklab
2023-10-17 8:21 dpdklab
2023-10-17 8:20 dpdklab
2023-10-17 8:20 dpdklab
2023-10-17 8:17 dpdklab
[not found] <20231017110655.582873-1-beilei.xing@intel.com>
2023-10-17 2:27 ` qemudev
2023-10-17 2:31 ` qemudev
2023-10-17 2:47 ` checkpatch
2023-10-17 3:39 ` 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=652e51c9.020a0220.615c9.2d42SMTPIN_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).