From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136180-136179 [PATCH] [2/2] dma/skeleton: support fill o
Date: Fri, 26 Jan 2024 02:24:18 -0800 (PST) [thread overview]
Message-ID: <65b38852.050a0220.f9966.2a8bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136179
_Testing PASS_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Friday, January 26 2024 08:57:26
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2ecc673e5e9a19850ba76d6a976596890f2dade1
136180-136179 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28971/
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-26 10:24 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 10:24 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-26 12:53 dpdklab
2024-01-26 11:37 dpdklab
2024-01-26 11:25 dpdklab
2024-01-26 11:17 dpdklab
2024-01-26 11:15 dpdklab
2024-01-26 11:13 dpdklab
2024-01-26 11:09 dpdklab
2024-01-26 11:04 dpdklab
2024-01-26 11:01 dpdklab
2024-01-26 11:01 dpdklab
2024-01-26 10:59 dpdklab
2024-01-26 10:57 dpdklab
2024-01-26 10:55 dpdklab
2024-01-26 10:52 dpdklab
2024-01-26 10:50 dpdklab
2024-01-26 10:50 dpdklab
2024-01-26 10:46 dpdklab
2024-01-26 10:46 dpdklab
2024-01-26 10:45 dpdklab
2024-01-26 10:45 dpdklab
2024-01-26 10:44 dpdklab
2024-01-26 10:43 dpdklab
2024-01-26 10:40 dpdklab
2024-01-26 10:39 dpdklab
2024-01-26 10:37 dpdklab
2024-01-26 10:37 dpdklab
2024-01-26 10:35 dpdklab
2024-01-26 10:32 dpdklab
2024-01-26 10:30 dpdklab
2024-01-26 10:29 dpdklab
2024-01-26 10:28 dpdklab
2024-01-26 10:25 dpdklab
2024-01-26 10:22 dpdklab
2024-01-26 10:21 dpdklab
2024-01-26 10:20 dpdklab
2024-01-26 10:20 dpdklab
2024-01-26 10:19 dpdklab
2024-01-26 10:19 dpdklab
2024-01-26 10:17 dpdklab
2024-01-26 10:17 dpdklab
2024-01-26 10:17 dpdklab
2024-01-26 10:17 dpdklab
2024-01-26 10:13 dpdklab
2024-01-26 10:13 dpdklab
2024-01-26 10:12 dpdklab
2024-01-26 10:12 dpdklab
2024-01-26 10:12 dpdklab
2024-01-26 10:12 dpdklab
2024-01-26 10:11 dpdklab
2024-01-26 10:11 dpdklab
2024-01-26 10:11 dpdklab
2024-01-26 10:11 dpdklab
2024-01-26 10:10 dpdklab
2024-01-26 10:10 dpdklab
2024-01-26 10:10 dpdklab
2024-01-26 10:10 dpdklab
2024-01-26 10:09 dpdklab
2024-01-26 10:09 dpdklab
2024-01-26 10:09 dpdklab
2024-01-26 10:08 dpdklab
2024-01-26 10:08 dpdklab
2024-01-26 10:07 dpdklab
2024-01-26 10:07 dpdklab
2024-01-26 10:07 dpdklab
2024-01-26 10:06 dpdklab
2024-01-26 10:06 dpdklab
2024-01-26 10:06 dpdklab
2024-01-26 10:03 dpdklab
2024-01-26 9:57 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=65b38852.050a0220.f9966.2a8bSMTPIN_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).