From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Chengwen Feng <fengchengwen@huawei.com>
Subject: |SUCCESS| pw135880 [PATCH] [v2] bus/uacce: introduce UACCE bus
Date: Mon, 15 Jan 2024 20:22:38 -0800 (PST) [thread overview]
Message-ID: <65a6048e.050a0220.af831.487bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135880
_Testing PASS_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Tuesday, January 16 2024 03:35:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d4af9a82063e4c39568191eaa12955d3ca39581a
135880 --> testing pass
Test environment and result as below:
+---------------------+--------------------+
| Environment | dpdk_meson_compile |
+=====================+====================+
| Windows Server 2022 | PASS |
+---------------------+--------------------+
| CentOS Stream 8 | PASS |
+---------------------+--------------------+
| FreeBSD 13 | PASS |
+---------------------+--------------------+
| Debian Bullseye | PASS |
+---------------------+--------------------+
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28868/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-16 4:22 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 4:22 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-16 17:16 dpdklab
2024-01-16 6:19 dpdklab
2024-01-16 5:52 dpdklab
2024-01-16 5:50 dpdklab
2024-01-16 5:50 dpdklab
2024-01-16 5:01 dpdklab
2024-01-16 5:00 dpdklab
2024-01-16 4:59 dpdklab
2024-01-16 4:57 dpdklab
2024-01-16 4:56 dpdklab
2024-01-16 4:51 dpdklab
2024-01-16 4:50 dpdklab
2024-01-16 4:49 dpdklab
2024-01-16 4:49 dpdklab
2024-01-16 4:48 dpdklab
2024-01-16 4:48 dpdklab
2024-01-16 4:48 dpdklab
2024-01-16 4:48 dpdklab
2024-01-16 4:48 dpdklab
2024-01-16 4:47 dpdklab
2024-01-16 4:47 dpdklab
2024-01-16 4:46 dpdklab
2024-01-16 4:45 dpdklab
2024-01-16 4:44 dpdklab
2024-01-16 4:44 dpdklab
2024-01-16 4:44 dpdklab
2024-01-16 4:43 dpdklab
2024-01-16 4:43 dpdklab
2024-01-16 4:42 dpdklab
2024-01-16 4:40 dpdklab
2024-01-16 4:39 dpdklab
2024-01-16 4:38 dpdklab
2024-01-16 4:38 dpdklab
2024-01-16 4:37 dpdklab
2024-01-16 4:36 dpdklab
2024-01-16 4:35 dpdklab
2024-01-16 4:35 dpdklab
2024-01-16 4:35 dpdklab
2024-01-16 4:34 dpdklab
2024-01-16 4:34 dpdklab
2024-01-16 4:34 dpdklab
2024-01-16 4:33 dpdklab
2024-01-16 4:32 dpdklab
2024-01-16 4:32 dpdklab
2024-01-16 4:32 dpdklab
2024-01-16 4:32 dpdklab
2024-01-16 4:31 dpdklab
2024-01-16 4:31 dpdklab
2024-01-16 4:31 dpdklab
2024-01-16 4:30 dpdklab
2024-01-16 4:30 dpdklab
2024-01-16 4:29 dpdklab
[not found] <20240116033543.24844-1-fengchengwen@huawei.com>
2024-01-16 3:17 ` |SUCCESS| pw135880 [PATCH v2] " qemudev
2024-01-16 3:21 ` qemudev
2024-01-16 4:29 ` 0-day Robot
2024-01-16 4:28 |SUCCESS| pw135880 [PATCH] [v2] " dpdklab
2024-01-16 4:28 dpdklab
2024-01-16 4:28 dpdklab
2024-01-16 4:26 dpdklab
2024-01-16 4:26 dpdklab
2024-01-16 4:25 dpdklab
2024-01-16 4:24 dpdklab
2024-01-16 4:24 dpdklab
2024-01-16 4:23 dpdklab
2024-01-16 4:23 dpdklab
2024-01-16 4:23 dpdklab
2024-01-16 4:23 dpdklab
2024-01-16 4:22 dpdklab
2024-01-16 4:21 dpdklab
2024-01-16 4:21 dpdklab
2024-01-16 4:20 dpdklab
2024-01-16 4:20 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=65a6048e.050a0220.af831.487bSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=fengchengwen@huawei.com \
--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).