From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134947 [PATCH] bus/uacce: introduce UACCE bus
Date: Fri, 08 Dec 2023 04:33:59 -0800 (PST) [thread overview]
Message-ID: <65730d37.4a0a0220.15de2.5d7dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/134947
_Testing PASS_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Friday, December 08 2023 06:18:36
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f2d5afbb2c05d7647da7ea914887c52115652651
134947 --> testing pass
Test environment and result as below:
+------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+====================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+------------------------------------+--------------------+
| CentOS Stream 9 (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)
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.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
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/28562/
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-08 12:34 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 12:33 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-09 1:11 dpdklab
2023-12-08 15:12 dpdklab
2023-12-08 13:02 dpdklab
2023-12-08 12:59 dpdklab
2023-12-08 12:44 dpdklab
2023-12-08 12:44 dpdklab
2023-12-08 12:42 dpdklab
2023-12-08 12:41 dpdklab
2023-12-08 12:40 dpdklab
2023-12-08 12:39 dpdklab
2023-12-08 12:38 dpdklab
2023-12-08 12:33 dpdklab
2023-12-08 12:32 dpdklab
2023-12-08 12:32 dpdklab
2023-12-08 12:31 dpdklab
2023-12-08 12:31 dpdklab
2023-12-08 12:31 dpdklab
2023-12-08 12:30 dpdklab
2023-12-08 12:30 dpdklab
2023-12-08 12:30 dpdklab
2023-12-08 12:30 dpdklab
2023-12-08 12:29 dpdklab
2023-12-08 12:29 dpdklab
2023-12-08 12:29 dpdklab
2023-12-08 12:29 dpdklab
2023-12-08 12:29 dpdklab
2023-12-08 12:28 dpdklab
2023-12-08 12:28 dpdklab
2023-12-08 12:28 dpdklab
2023-12-08 12:27 dpdklab
2023-12-08 12:27 dpdklab
2023-12-08 12:27 dpdklab
2023-12-08 12:27 dpdklab
2023-12-08 12:27 dpdklab
2023-12-08 12:26 dpdklab
2023-12-08 12:26 dpdklab
2023-12-08 12:26 dpdklab
2023-12-08 12:25 dpdklab
2023-12-08 12:24 dpdklab
2023-12-08 12:24 dpdklab
2023-12-08 12:24 dpdklab
2023-12-08 12:23 dpdklab
2023-12-08 12:23 dpdklab
2023-12-08 12:22 dpdklab
2023-12-08 12:22 dpdklab
2023-12-08 12:22 dpdklab
2023-12-08 12:21 dpdklab
2023-12-08 12:21 dpdklab
2023-12-08 12:20 dpdklab
2023-12-08 12:20 dpdklab
2023-12-08 12:19 dpdklab
2023-12-08 12:12 dpdklab
2023-12-08 12:12 dpdklab
2023-12-08 12:11 dpdklab
2023-12-08 12:01 dpdklab
2023-12-08 12:01 dpdklab
2023-12-08 12:00 dpdklab
2023-12-08 11:59 dpdklab
2023-12-08 11:58 dpdklab
2023-12-08 11:58 dpdklab
2023-12-08 11:58 dpdklab
2023-12-08 11:53 dpdklab
2023-12-08 11:50 dpdklab
2023-12-08 11:46 dpdklab
[not found] <20231208061836.31693-1-fengchengwen@huawei.com>
2023-12-08 6:11 ` qemudev
2023-12-08 6:15 ` qemudev
2023-12-08 7:20 ` 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=65730d37.4a0a0220.15de2.5d7dSMTPIN_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).