From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw153363-153369 [PATCH] [v1,7/7] event/dlb2: fix default c
Date: Thu, 08 May 2025 23:24:17 -0700 (PDT) [thread overview]
Message-ID: <681d9f91.050a0220.27873.333fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250509042401.2634765-8-pravin.pathak@intel.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/153369
_Testing PASS_
Submitter: Pravin Pathak <pravin.pathak@intel.com>
Date: Friday, May 09 2025 04:24:01
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2a5c6c4709c9a23feb92ed1325945cb459884b4f
153363-153369 --> testing pass
Upstream job id: Windows-Compile-DPDK-Native#28310
Test environment and result as below:
+---------------------+--------------------+-------------------+-------------------------+
| Environment | dpdk_meson_compile | dpdk_msvc_compile | dpdk_llvm_clang_compile |
+=====================+====================+===================+=========================+
| Ubuntu 20.04 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+-------------------------+
| FreeBSD 13.5 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+-------------------------+
| FreeBSD 14.2 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+-------------------------+
| Windows Server 2022 | SKIPPED | PASS | PASS |
+---------------------+--------------------+-------------------+-------------------------+
Ubuntu 20.04
Kernel: 4.19.325-0419325-generic
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
FreeBSD 13.5
Kernel: 13.5-RELEASE
Compiler: clang 19.1.7
FreeBSD 14.2
Kernel: 14.2-RELEASE
Compiler: clang 18.1.6
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33145/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-05-09 6:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250509042401.2634765-8-pravin.pathak@intel.com>
2025-05-09 3:59 ` |SUCCESS| pw153363-153369 [PATCH v1 7/7] event/dlb2: fix default credits in dlb2_eventdev_info_get() qemudev
2025-05-09 4:03 ` qemudev
2025-05-09 4:25 ` |SUCCESS| pw153369 [PATCH v1 7/7] event/dlb2: fix default credits in dlb2_eventdev_info_get checkpatch
2025-05-09 5:45 ` |SUCCESS| pw153363-153369 [PATCH] [v1,7/7] event/dlb2: fix default c dpdklab
2025-05-09 5:53 ` dpdklab
2025-05-09 6:00 ` dpdklab
2025-05-09 6:02 ` dpdklab
2025-05-09 6:07 ` dpdklab
2025-05-09 6:17 ` dpdklab
2025-05-09 6:24 ` dpdklab [this message]
2025-05-09 6:28 ` dpdklab
2025-05-09 6:32 ` dpdklab
2025-05-09 6:35 ` |PENDING| " dpdklab
2025-05-09 6:47 ` dpdklab
2025-05-09 6:47 ` |SUCCESS| " dpdklab
2025-05-09 7:06 ` dpdklab
2025-05-09 7:13 ` dpdklab
2025-05-09 7:29 ` |PENDING| " dpdklab
2025-05-09 7:30 ` |SUCCESS| " dpdklab
2025-05-09 8:22 ` dpdklab
2025-05-09 8:25 ` |PENDING| " dpdklab
2025-05-09 9:11 ` |SUCCESS| " dpdklab
2025-05-09 9:23 ` dpdklab
2025-05-09 10:07 ` dpdklab
2025-05-09 10:46 ` dpdklab
2025-05-09 11:11 ` 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=681d9f91.050a0220.27873.333fSMTPIN_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).