From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136652 [PATCH] [1/1] maintainers: update RISC-V maintain
Date: Tue, 13 Feb 2024 17:22:12 -0800 (PST) [thread overview]
Message-ID: <65cc15c4.170a0220.93911.0ddaSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136652
_Testing PASS_
Submitter: Stanislaw Kardach <kda@semihalf.com>
Date: Tuesday, February 13 2024 18:14:07
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:31d72ff4dc7c057366153e9918ac92bf9123a3bc
136652 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
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)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29138/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-14 1:22 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 1:22 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-14 7:58 dpdklab
2024-02-14 5:33 dpdklab
2024-02-14 4:48 dpdklab
2024-02-14 3:46 dpdklab
2024-02-14 3:40 dpdklab
2024-02-14 3:23 dpdklab
2024-02-14 3:23 dpdklab
2024-02-14 3:23 dpdklab
2024-02-14 3:12 dpdklab
2024-02-14 3:07 dpdklab
2024-02-14 3:06 dpdklab
2024-02-14 3:06 dpdklab
2024-02-14 3:05 dpdklab
2024-02-14 3:05 dpdklab
2024-02-14 3:05 dpdklab
2024-02-14 3:04 dpdklab
2024-02-14 3:04 dpdklab
2024-02-14 3:01 dpdklab
2024-02-14 3:01 dpdklab
2024-02-14 2:54 dpdklab
2024-02-14 2:50 dpdklab
2024-02-14 2:48 dpdklab
2024-02-14 2:48 dpdklab
2024-02-14 2:45 dpdklab
2024-02-14 2:44 dpdklab
2024-02-14 2:42 dpdklab
2024-02-14 2:42 dpdklab
2024-02-14 2:42 dpdklab
2024-02-14 2:41 dpdklab
2024-02-14 2:41 dpdklab
2024-02-14 2:41 dpdklab
2024-02-14 2:40 dpdklab
2024-02-14 2:40 dpdklab
2024-02-14 2:39 dpdklab
2024-02-14 2:39 dpdklab
2024-02-14 2:39 dpdklab
2024-02-14 2:39 dpdklab
2024-02-14 2:38 dpdklab
2024-02-14 2:38 dpdklab
2024-02-14 2:37 dpdklab
2024-02-14 2:37 dpdklab
2024-02-14 2:37 dpdklab
2024-02-14 2:37 dpdklab
2024-02-14 2:36 dpdklab
2024-02-14 2:36 dpdklab
2024-02-14 2:31 dpdklab
2024-02-14 2:27 dpdklab
2024-02-14 1:29 dpdklab
2024-02-14 1:22 dpdklab
2024-02-14 1:21 dpdklab
2024-02-14 1:14 dpdklab
2024-02-14 1:13 dpdklab
2024-02-14 1:13 dpdklab
2024-02-14 1:09 dpdklab
2024-02-14 1:08 dpdklab
2024-02-14 1:07 dpdklab
2024-02-14 1:07 dpdklab
2024-02-14 1:07 dpdklab
2024-02-14 1:07 dpdklab
2024-02-14 1:07 dpdklab
2024-02-14 1:06 dpdklab
2024-02-14 1:06 dpdklab
2024-02-14 1:01 dpdklab
2024-02-14 1:01 dpdklab
2024-02-14 0:53 dpdklab
2024-02-14 0:51 dpdklab
2024-02-14 0:48 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=65cc15c4.170a0220.93911.0ddaSMTPIN_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).