From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136957-136968 [PATCH] [v4,12/12] eventdev: fix doxygen p
Date: Wed, 21 Feb 2024 09:34:25 -0800 (PST) [thread overview]
Message-ID: <65d63421.170a0220.779a6.9bf4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136968
_Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Wednesday, February 21 2024 10:32:21
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2423ba36ed1e9302dc6644ff777a1a0254dea12e
136957-136968 --> 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/29211/
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-21 17:34 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 17:34 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-23 5:51 dpdklab
2024-02-23 5:35 dpdklab
2024-02-21 21:15 dpdklab
2024-02-21 20:59 dpdklab
2024-02-21 20:48 dpdklab
2024-02-21 20:40 dpdklab
2024-02-21 20:22 dpdklab
2024-02-21 20:17 dpdklab
2024-02-21 20:14 dpdklab
2024-02-21 20:05 dpdklab
2024-02-21 20:04 dpdklab
2024-02-21 19:59 dpdklab
2024-02-21 19:57 dpdklab
2024-02-21 19:53 dpdklab
2024-02-21 19:50 dpdklab
2024-02-21 19:45 dpdklab
2024-02-21 19:25 dpdklab
2024-02-21 19:19 dpdklab
2024-02-21 19:14 dpdklab
2024-02-21 19:09 dpdklab
2024-02-21 18:54 dpdklab
2024-02-21 18:49 dpdklab
2024-02-21 18:43 dpdklab
2024-02-21 18:42 dpdklab
2024-02-21 18:41 dpdklab
2024-02-21 18:40 dpdklab
2024-02-21 18:38 dpdklab
2024-02-21 18:34 dpdklab
2024-02-21 18:33 dpdklab
2024-02-21 18:31 dpdklab
2024-02-21 18:28 dpdklab
2024-02-21 18:28 dpdklab
2024-02-21 18:25 dpdklab
2024-02-21 18:23 dpdklab
2024-02-21 18:22 dpdklab
2024-02-21 18:22 dpdklab
2024-02-21 18:21 dpdklab
2024-02-21 18:19 dpdklab
2024-02-21 18:15 dpdklab
2024-02-21 18:13 dpdklab
2024-02-21 18:12 dpdklab
2024-02-21 18:11 dpdklab
2024-02-21 18:10 dpdklab
2024-02-21 18:06 dpdklab
2024-02-21 18:06 dpdklab
2024-02-21 18:06 dpdklab
2024-02-21 18:06 dpdklab
2024-02-21 18:04 dpdklab
2024-02-21 18:01 dpdklab
2024-02-21 18:00 dpdklab
2024-02-21 17:57 dpdklab
2024-02-21 17:56 dpdklab
2024-02-21 17:56 dpdklab
2024-02-21 17:56 dpdklab
2024-02-21 17:53 dpdklab
2024-02-21 17:53 dpdklab
2024-02-21 17:52 dpdklab
2024-02-21 17:52 dpdklab
2024-02-21 17:46 dpdklab
2024-02-21 17:46 dpdklab
2024-02-21 17:46 dpdklab
2024-02-21 17:45 dpdklab
2024-02-21 17:45 dpdklab
2024-02-21 17:43 dpdklab
2024-02-21 17:43 dpdklab
2024-02-21 17:42 dpdklab
2024-02-21 17:37 dpdklab
2024-02-21 17:37 dpdklab
2024-02-21 17:37 dpdklab
2024-02-21 17:37 dpdklab
2024-02-21 17:37 dpdklab
2024-02-21 17:33 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=65d63421.170a0220.779a6.9bf4SMTPIN_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).