From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141533-141553 [PATCH] [v5,21/21] doc: updated the docume
Date: Mon, 24 Jun 2024 11:06:15 -0700 (PDT) [thread overview]
Message-ID: <6679b597.050a0220.6023a.4b04SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240624091644.2404658-22-soumyadeep.hore@intel.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/141553
_Testing PASS_
Submitter: Soumyadeep Hore <soumyadeep.hore@intel.com>
Date: Monday, June 24 2024 09:16:44
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:eabbac98af1345157e07c431e18543296c37c355
141533-141553 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | 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
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30288/
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-06-24 18:06 UTC|newest]
Thread overview: 114+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240624091644.2404658-22-soumyadeep.hore@intel.com>
2024-06-24 9:41 ` |SUCCESS| pw141533-141553 [PATCH v5 21/21] doc: updated the documentation for cpfl PMD qemudev
2024-06-24 9:46 ` qemudev
2024-06-24 10:06 ` |SUCCESS| pw141553 " checkpatch
2024-06-24 11:04 ` 0-day Robot
2024-06-24 14:26 ` |SUCCESS| pw141533-141553 [PATCH] [v5,21/21] doc: updated the docume dpdklab
2024-06-24 14:26 ` dpdklab
2024-06-24 14:28 ` dpdklab
2024-06-24 14:28 ` dpdklab
2024-06-24 14:29 ` dpdklab
2024-06-24 14:30 ` dpdklab
2024-06-24 14:31 ` dpdklab
2024-06-24 14:32 ` dpdklab
2024-06-24 14:36 ` dpdklab
2024-06-24 14:38 ` dpdklab
2024-06-24 14:46 ` dpdklab
2024-06-24 14:46 ` dpdklab
2024-06-24 14:58 ` dpdklab
2024-06-24 15:17 ` dpdklab
2024-06-24 15:19 ` dpdklab
2024-06-24 15:26 ` dpdklab
2024-06-24 15:27 ` dpdklab
2024-06-24 15:58 ` dpdklab
2024-06-24 16:00 ` dpdklab
2024-06-24 16:00 ` dpdklab
2024-06-24 16:00 ` dpdklab
2024-06-24 16:02 ` dpdklab
2024-06-24 16:05 ` dpdklab
2024-06-24 16:05 ` dpdklab
2024-06-24 16:07 ` dpdklab
2024-06-24 16:07 ` dpdklab
2024-06-24 16:07 ` dpdklab
2024-06-24 16:33 ` dpdklab
2024-06-24 16:33 ` dpdklab
2024-06-24 16:34 ` dpdklab
2024-06-24 16:34 ` dpdklab
2024-06-24 16:39 ` dpdklab
2024-06-24 16:41 ` dpdklab
2024-06-24 16:41 ` dpdklab
2024-06-24 16:42 ` dpdklab
2024-06-24 16:42 ` dpdklab
2024-06-24 16:42 ` dpdklab
2024-06-24 16:43 ` dpdklab
2024-06-24 16:43 ` dpdklab
2024-06-24 16:44 ` dpdklab
2024-06-24 16:46 ` dpdklab
2024-06-24 16:47 ` dpdklab
2024-06-24 16:58 ` dpdklab
2024-06-24 16:59 ` dpdklab
2024-06-24 17:04 ` dpdklab
2024-06-24 17:11 ` dpdklab
2024-06-24 17:19 ` dpdklab
2024-06-24 17:21 ` dpdklab
2024-06-24 17:31 ` dpdklab
2024-06-24 17:34 ` dpdklab
2024-06-24 17:39 ` dpdklab
2024-06-24 17:41 ` dpdklab
2024-06-24 17:46 ` dpdklab
2024-06-24 17:49 ` dpdklab
2024-06-24 17:49 ` dpdklab
2024-06-24 17:52 ` dpdklab
2024-06-24 18:00 ` dpdklab
2024-06-24 18:06 ` dpdklab [this message]
2024-06-24 18:11 ` dpdklab
2024-06-24 18:11 ` dpdklab
2024-06-24 18:16 ` dpdklab
2024-06-24 18:18 ` dpdklab
2024-06-24 18:18 ` dpdklab
2024-06-24 18:19 ` dpdklab
2024-06-24 18:23 ` dpdklab
2024-06-24 18:23 ` dpdklab
2024-06-24 18:23 ` dpdklab
2024-06-24 18:28 ` dpdklab
2024-06-24 18:31 ` dpdklab
2024-06-24 18:38 ` dpdklab
2024-06-24 18:43 ` dpdklab
2024-06-24 18:44 ` dpdklab
2024-06-24 18:45 ` dpdklab
2024-06-24 18:56 ` dpdklab
2024-06-24 18:57 ` dpdklab
2024-06-24 18:59 ` dpdklab
2024-06-24 19:00 ` dpdklab
2024-06-24 19:01 ` dpdklab
2024-06-24 19:01 ` dpdklab
2024-06-24 19:02 ` dpdklab
2024-06-24 19:06 ` dpdklab
2024-06-24 19:11 ` dpdklab
2024-06-24 19:11 ` dpdklab
2024-06-24 19:14 ` dpdklab
2024-06-24 19:16 ` dpdklab
2024-06-24 19:17 ` dpdklab
2024-06-24 19:23 ` dpdklab
2024-06-24 19:30 ` dpdklab
2024-06-24 19:31 ` dpdklab
2024-06-24 19:32 ` dpdklab
2024-06-24 19:37 ` dpdklab
2024-06-24 19:42 ` dpdklab
2024-06-24 19:44 ` dpdklab
2024-06-24 19:47 ` dpdklab
2024-06-24 19:51 ` dpdklab
2024-06-24 19:55 ` dpdklab
2024-06-24 19:56 ` dpdklab
2024-06-24 19:58 ` dpdklab
2024-06-24 20:05 ` dpdklab
2024-06-24 20:11 ` dpdklab
2024-06-24 20:14 ` dpdklab
2024-06-24 20:15 ` dpdklab
2024-06-24 20:18 ` dpdklab
2024-06-24 20:20 ` dpdklab
2024-06-24 20:23 ` dpdklab
2024-06-24 20:30 ` dpdklab
2024-06-24 20:39 ` dpdklab
2024-06-24 21:53 ` dpdklab
2024-06-24 22:26 ` dpdklab
2024-06-25 0:08 ` 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=6679b597.050a0220.6023a.4b04SMTPIN_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).