From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137036 [PATCH] [v2] net/af_xdp: fix resources leak when
Date: Thu, 22 Feb 2024 09:07:38 -0800 (PST) [thread overview]
Message-ID: <65d77f5a.810a0220.63d49.4713SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137036
_Testing PASS_
Submitter: Yunjian Wang <wangyunjian@huawei.com>
Date: Thursday, February 22 2024 13:35:39
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:dee3c01a2297538d7b65048aedfb372464f89942
137036 --> testing pass
Test environment and result as below:
+--------------------------+--------------+----------------+
| Environment | lpm_autotest | dpdk_unit_test |
+==========================+==============+================+
| Ubuntu 20.04 ARM SVE | PASS | SKIPPED |
+--------------------------+--------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED | PASS |
+--------------------------+--------------+----------------+
| CentOS Stream 9 (ARM) | SKIPPED | PASS |
+--------------------------+--------------+----------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29225/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-22 17:07 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 17:07 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-24 1:12 dpdklab
2024-02-23 3:04 dpdklab
2024-02-23 2:57 dpdklab
2024-02-22 23:16 dpdklab
2024-02-22 17:36 dpdklab
2024-02-22 17:32 dpdklab
2024-02-22 17:29 dpdklab
2024-02-22 17:26 dpdklab
2024-02-22 17:19 dpdklab
2024-02-22 17:12 dpdklab
2024-02-22 17:05 dpdklab
2024-02-22 16:47 dpdklab
2024-02-22 16:05 dpdklab
2024-02-22 16:01 dpdklab
2024-02-22 15:51 dpdklab
2024-02-22 15:31 dpdklab
2024-02-22 15:31 dpdklab
2024-02-22 15:30 dpdklab
2024-02-22 15:30 dpdklab
2024-02-22 15:27 dpdklab
2024-02-22 15:26 dpdklab
2024-02-22 15:26 dpdklab
2024-02-22 15:24 dpdklab
2024-02-22 15:24 dpdklab
2024-02-22 15:22 dpdklab
2024-02-22 15:19 dpdklab
2024-02-22 15:17 dpdklab
2024-02-22 15:15 dpdklab
2024-02-22 15:15 dpdklab
2024-02-22 15:14 dpdklab
2024-02-22 15:13 dpdklab
2024-02-22 15:06 dpdklab
2024-02-22 15:05 dpdklab
2024-02-22 14:36 dpdklab
2024-02-22 14:30 dpdklab
2024-02-22 14:27 dpdklab
2024-02-22 14:26 dpdklab
2024-02-22 14:24 dpdklab
2024-02-22 14:24 dpdklab
2024-02-22 14:24 dpdklab
2024-02-22 14:24 dpdklab
2024-02-22 14:23 dpdklab
2024-02-22 14:23 dpdklab
2024-02-22 14:22 dpdklab
2024-02-22 14:21 dpdklab
2024-02-22 14:21 dpdklab
2024-02-22 14:20 dpdklab
2024-02-22 14:17 dpdklab
2024-02-22 14:15 dpdklab
2024-02-22 14:15 dpdklab
2024-02-22 14:14 dpdklab
2024-02-22 14:13 dpdklab
2024-02-22 14:13 dpdklab
2024-02-22 14:11 dpdklab
2024-02-22 14:10 dpdklab
2024-02-22 14:10 dpdklab
2024-02-22 14:09 dpdklab
2024-02-22 14:08 dpdklab
2024-02-22 14:08 dpdklab
2024-02-22 14:08 dpdklab
2024-02-22 14:07 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=65d77f5a.810a0220.63d49.4713SMTPIN_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).