From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw144269 [PATCH] [v3] ethdev: optimize the activation of f
Date: Wed, 18 Sep 2024 19:20:17 -0700 (PDT) [thread overview]
Message-ID: <66eb8a61.050a0220.19a6ae.d7ccSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240918184502.125550-1-adel.belkhiri@gmail.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/144269
_Testing PASS_
Submitter: Adel Belkhiri <adel.belkhiri@gmail.com>
Date: Wednesday, September 18 2024 18:45:02
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:523fd7b3adfdf5a87651e8ca33bc69223b3211d5
144269 --> testing pass
Upstream job id: Windows-Compile-DPDK-VS#3149
Test environment and result as below:
+---------------------+-----------------------+----------------------+--------------------+-------------------+
| Environment | dpdk_win_llvm_compile | dpdk_mingw64_compile | dpdk_meson_compile | dpdk_msvc_compile |
+=====================+=======================+======================+====================+===================+
| Windows Server 2022 | PASS | PASS | SKIPPED | PASS |
+---------------------+-----------------------+----------------------+--------------------+-------------------+
| FreeBSD 13.3 | SKIPPED | SKIPPED | PASS | SKIPPED |
+---------------------+-----------------------+----------------------+--------------------+-------------------+
| FreeBSD 14.1 | SKIPPED | SKIPPED | PASS | SKIPPED |
+---------------------+-----------------------+----------------------+--------------------+-------------------+
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
FreeBSD 13.3
Kernel: 13.3-RELEASE-p5
Compiler: clang 17.0.6
FreeBSD 14.1
Kernel: 14.1-RELEASE-p3
Compiler: clang 18.1.5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31072/
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:[~2024-09-19 2:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240918184502.125550-1-adel.belkhiri@gmail.com>
2024-09-18 18:19 ` |SUCCESS| pw144269 [PATCH v3] ethdev: optimize the activation of fast-path tracepoints qemudev
2024-09-18 18:23 ` qemudev
2024-09-18 18:47 ` checkpatch
2024-09-18 19:44 ` 0-day Robot
2024-09-18 21:40 ` |SUCCESS| pw144269 [PATCH] [v3] ethdev: optimize the activation of f dpdklab
2024-09-18 22:16 ` dpdklab
2024-09-18 23:25 ` |FAILURE| " dpdklab
2024-09-19 0:50 ` |PENDING| " dpdklab
2024-09-19 1:01 ` |SUCCESS| " dpdklab
2024-09-19 1:17 ` |PENDING| " dpdklab
2024-09-19 2:07 ` dpdklab
2024-09-19 2:20 ` dpdklab [this message]
2024-09-19 3:14 ` |SUCCESS| " dpdklab
2024-09-19 3:57 ` dpdklab
2024-09-19 5:13 ` dpdklab
2024-09-19 5:17 ` dpdklab
2024-09-19 5:25 ` |PENDING| " dpdklab
2024-09-19 5:37 ` |SUCCESS| " dpdklab
2024-09-19 6:20 ` dpdklab
2024-09-19 8:24 ` dpdklab
2024-09-19 8:26 ` dpdklab
2024-09-19 9:00 ` 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=66eb8a61.050a0220.19a6ae.d7ccSMTPIN_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).