From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142731 [PATCH] doc: announce fib configuration structure
Date: Fri, 26 Jul 2024 17:28:41 -0700 (PDT) [thread overview]
Message-ID: <66a43f39.050a0220.3cdfe1.8f50SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240726161333.878004-1-vladimir.medvedkin@intel.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/142731
_Testing PASS_
Submitter: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Date: Friday, July 26 2024 16:13:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:82c47f005b9a0a1e3a649664b7713443d18abe43
142731 --> testing pass
Upstream job id: Generic-VM-Unit-Test-DPDK#24409
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30631/
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-07-27 0:28 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240726161333.878004-1-vladimir.medvedkin@intel.com>
2024-07-26 15:46 ` |SUCCESS| pw142731 [PATCH] doc: announce fib configuration structure changes qemudev
2024-07-26 15:51 ` qemudev
2024-07-26 16:15 ` checkpatch
2024-07-26 17:03 ` 0-day Robot
2024-07-26 21:52 ` |SUCCESS| pw142731 [PATCH] doc: announce fib configuration structure dpdklab
2024-07-26 22:16 ` |PENDING| " dpdklab
2024-07-26 22:24 ` dpdklab
2024-07-26 22:28 ` |SUCCESS| " dpdklab
2024-07-26 22:29 ` dpdklab
2024-07-26 22:36 ` dpdklab
2024-07-26 22:37 ` dpdklab
2024-07-26 22:50 ` dpdklab
2024-07-26 23:06 ` dpdklab
2024-07-26 23:13 ` |PENDING| " dpdklab
2024-07-27 0:18 ` dpdklab
2024-07-27 0:21 ` dpdklab
2024-07-27 0:22 ` dpdklab
2024-07-27 0:26 ` dpdklab
2024-07-27 0:26 ` dpdklab
2024-07-27 0:26 ` dpdklab
2024-07-27 0:28 ` dpdklab [this message]
2024-07-27 0:29 ` dpdklab
2024-07-27 0:32 ` dpdklab
2024-07-27 0:37 ` dpdklab
2024-07-27 0:45 ` dpdklab
2024-07-27 0:55 ` dpdklab
2024-07-27 0:59 ` dpdklab
2024-07-27 0:59 ` dpdklab
2024-07-27 1:02 ` dpdklab
2024-07-27 1:06 ` dpdklab
2024-07-27 1:07 ` dpdklab
2024-07-27 1:12 ` dpdklab
2024-07-27 1:13 ` |SUCCESS| " dpdklab
2024-07-27 1:14 ` |PENDING| " dpdklab
2024-07-27 1:14 ` dpdklab
2024-07-27 1:19 ` dpdklab
2024-07-27 1:22 ` dpdklab
2024-07-27 1:24 ` dpdklab
2024-07-27 2:57 ` |SUCCESS| " 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=66a43f39.050a0220.3cdfe1.8f50SMTPIN_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).