From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143760 [PATCH] fib: implement RCU rule reclamation
Date: Fri, 06 Sep 2024 17:07:49 -0700 (PDT) [thread overview]
Message-ID: <66db9955.810a0220.39f1f.108aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240906170907.1325808-1-vladimir.medvedkin@intel.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/143760
_Testing PASS_
Submitter: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Date: Friday, September 06 2024 17:09:07
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43
143760 --> testing pass
Upstream job id: Windows-Compile-DPDK-VS#3020
Test environment and result as below:
+---------------------+----------------------+-----------------------+--------------------+-------------------+
| Environment | dpdk_mingw64_compile | dpdk_win_llvm_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/30951/
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-07 0:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240906170907.1325808-1-vladimir.medvedkin@intel.com>
2024-09-06 16:41 ` qemudev
2024-09-06 16:46 ` qemudev
2024-09-06 17:10 ` |WARNING| " checkpatch
2024-09-06 18:05 ` |FAILURE| " 0-day Robot
2024-09-06 21:49 ` |SUCCESS| " dpdklab
2024-09-06 21:51 ` dpdklab
2024-09-06 21:52 ` dpdklab
2024-09-06 21:54 ` dpdklab
2024-09-06 22:03 ` dpdklab
2024-09-06 22:17 ` dpdklab
2024-09-06 22:52 ` |PENDING| " dpdklab
2024-09-06 23:40 ` dpdklab
2024-09-07 0:07 ` dpdklab [this message]
2024-09-07 3:44 ` |SUCCESS| " dpdklab
2024-09-07 4:45 ` dpdklab
2024-09-07 4:46 ` dpdklab
2024-09-07 8:13 ` dpdklab
2024-09-07 8:18 ` dpdklab
2024-09-07 8:23 ` dpdklab
2024-09-07 8:29 ` dpdklab
2024-09-07 8:48 ` dpdklab
2024-09-07 14:25 ` dpdklab
2024-09-07 15:21 ` dpdklab
2024-09-07 16:08 ` dpdklab
2024-09-08 9:36 ` dpdklab
2024-09-17 3:14 ` dpdklab
2024-09-17 3:32 ` 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=66db9955.810a0220.39f1f.108aSMTPIN_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).