From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134741 [PATCH] net/af_xdp: fix memzone leak in error pat
Date: Fri, 01 Dec 2023 02:32:50 -0800 (PST) [thread overview]
Message-ID: <6569b652.0d0a0220.515b3.cc82SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/134741
_Testing PASS_
Submitter: Yunjian Wang <wangyunjian@huawei.com>
Date: Friday, December 01 2023 08:03:07
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c858f006d1f7161986c88847259a400d8f80d81b
134741 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28506/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-01 10:32 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 10:32 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-01 15:43 dpdklab
2023-12-01 13:49 dpdklab
2023-12-01 13:00 dpdklab
2023-12-01 12:16 dpdklab
2023-12-01 12:10 dpdklab
2023-12-01 11:51 dpdklab
2023-12-01 11:44 dpdklab
2023-12-01 11:43 dpdklab
2023-12-01 11:40 dpdklab
2023-12-01 11:39 dpdklab
2023-12-01 11:29 dpdklab
2023-12-01 11:09 dpdklab
2023-12-01 11:06 dpdklab
2023-12-01 11:03 dpdklab
2023-12-01 11:02 dpdklab
2023-12-01 10:57 dpdklab
2023-12-01 10:55 dpdklab
2023-12-01 10:40 dpdklab
2023-12-01 10:33 dpdklab
2023-12-01 10:33 dpdklab
2023-12-01 10:32 dpdklab
2023-12-01 10:32 dpdklab
2023-12-01 10:32 dpdklab
2023-12-01 10:31 dpdklab
2023-12-01 10:31 dpdklab
2023-12-01 10:31 dpdklab
2023-12-01 10:31 dpdklab
2023-12-01 10:31 dpdklab
2023-12-01 10:31 dpdklab
2023-12-01 10:30 dpdklab
2023-12-01 10:30 dpdklab
2023-12-01 10:29 dpdklab
2023-12-01 10:29 dpdklab
2023-12-01 10:29 dpdklab
2023-12-01 10:28 dpdklab
2023-12-01 10:28 dpdklab
2023-12-01 10:28 dpdklab
2023-12-01 10:28 dpdklab
2023-12-01 10:27 dpdklab
2023-12-01 10:26 dpdklab
2023-12-01 10:25 dpdklab
2023-12-01 10:23 dpdklab
2023-12-01 10:23 dpdklab
2023-12-01 10:22 dpdklab
2023-12-01 10:22 dpdklab
2023-12-01 10:22 dpdklab
2023-12-01 10:22 dpdklab
2023-12-01 10:22 dpdklab
2023-12-01 10:22 dpdklab
2023-12-01 10:22 dpdklab
2023-12-01 10:21 dpdklab
2023-12-01 10:18 dpdklab
2023-12-01 10:09 dpdklab
2023-12-01 9:45 dpdklab
2023-12-01 9:44 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=6569b652.0d0a0220.515b3.cc82SMTPIN_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).