From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133077 [PATCH] mempool: fix internal function documentat
Date: Fri, 20 Oct 2023 11:20:28 -0700 (PDT) [thread overview]
Message-ID: <6532c4ec.810a0220.f01b8.9573SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133077
_Testing PASS_
Submitter: Ferruh Yigit <ferruh.yigit@amd.com>
Date: Friday, October 20 2023 14:46:46
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2cd2cf0cc53a508c4bd951a980ec534a646260de
133077 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28022/
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-20 18:20 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 18:20 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-20 19:47 dpdklab
2023-10-20 19:32 dpdklab
2023-10-20 18:37 dpdklab
2023-10-20 18:35 dpdklab
2023-10-20 18:35 dpdklab
2023-10-20 18:32 dpdklab
2023-10-20 18:30 dpdklab
2023-10-20 18:29 dpdklab
2023-10-20 18:29 dpdklab
2023-10-20 18:28 dpdklab
2023-10-20 18:28 dpdklab
2023-10-20 18:27 dpdklab
2023-10-20 18:27 dpdklab
2023-10-20 18:27 dpdklab
2023-10-20 18:26 dpdklab
2023-10-20 18:26 dpdklab
2023-10-20 18:26 dpdklab
2023-10-20 18:26 dpdklab
2023-10-20 18:26 dpdklab
2023-10-20 18:26 dpdklab
2023-10-20 18:25 dpdklab
2023-10-20 18:25 dpdklab
2023-10-20 18:25 dpdklab
2023-10-20 18:25 dpdklab
2023-10-20 18:25 dpdklab
2023-10-20 18:24 dpdklab
2023-10-20 18:20 dpdklab
2023-10-20 18:20 dpdklab
2023-10-20 18:20 dpdklab
2023-10-20 18:20 dpdklab
2023-10-20 18:20 dpdklab
2023-10-20 18:20 dpdklab
2023-10-20 18:20 dpdklab
2023-10-20 18:20 dpdklab
2023-10-20 18:20 dpdklab
2023-10-20 18:20 dpdklab
2023-10-20 18:20 dpdklab
2023-10-20 18:17 dpdklab
2023-10-20 18:17 dpdklab
2023-10-20 18:17 dpdklab
2023-10-20 18:17 dpdklab
2023-10-20 18:17 dpdklab
2023-10-20 18:17 dpdklab
2023-10-20 18:17 dpdklab
2023-10-20 18:16 dpdklab
2023-10-20 18:16 dpdklab
2023-10-20 18:16 dpdklab
2023-10-20 18:16 dpdklab
2023-10-20 18:16 dpdklab
2023-10-20 18:12 dpdklab
2023-10-20 18:12 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=6532c4ec.810a0220.f01b8.9573SMTPIN_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).