From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134634-134633 [PATCH] [v5,3/3] doc: add dump device priv
Date: Tue, 28 Nov 2023 02:21:22 -0800 (PST) [thread overview]
Message-ID: <6565bf22.050a0220.657f9.f62bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/134633
_Testing PASS_
Submitter: Huisong Li <lihuisong@huawei.com>
Date: Tuesday, November 28 2023 05:59:27
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3b3af56d3c9c472f9ba0ee1078d714919cc2b6b4
134634-134633 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28481/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-28 10:21 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 10:21 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-28 12:36 dpdklab
2023-11-28 10:48 dpdklab
2023-11-28 10:48 dpdklab
2023-11-28 10:45 dpdklab
2023-11-28 10:44 dpdklab
2023-11-28 10:41 dpdklab
2023-11-28 10:36 dpdklab
2023-11-28 10:33 dpdklab
2023-11-28 10:32 dpdklab
2023-11-28 10:28 dpdklab
2023-11-28 10:25 dpdklab
2023-11-28 10:21 dpdklab
2023-11-28 10:20 dpdklab
2023-11-28 10:19 dpdklab
2023-11-28 10:18 dpdklab
2023-11-28 10:12 dpdklab
2023-11-28 10:11 dpdklab
2023-11-28 10:10 dpdklab
2023-11-28 10:09 dpdklab
2023-11-28 10:04 dpdklab
2023-11-28 10:04 dpdklab
2023-11-28 10:03 dpdklab
2023-11-28 9:58 dpdklab
2023-11-28 9:58 dpdklab
2023-11-28 9:56 dpdklab
2023-11-28 9:54 dpdklab
2023-11-28 9:49 dpdklab
2023-11-28 9:48 dpdklab
2023-11-28 9:47 dpdklab
2023-11-28 9:47 dpdklab
2023-11-28 9:47 dpdklab
2023-11-28 9:46 dpdklab
2023-11-28 9:43 dpdklab
2023-11-28 9:42 dpdklab
2023-11-28 9:41 dpdklab
2023-11-28 9:27 dpdklab
2023-11-28 9:16 dpdklab
2023-11-28 9:15 dpdklab
2023-11-28 9:14 dpdklab
2023-11-28 9:11 dpdklab
2023-11-28 9:10 dpdklab
2023-11-28 9:09 dpdklab
2023-11-28 9:09 dpdklab
2023-11-28 9:08 dpdklab
2023-11-28 9:08 dpdklab
2023-11-28 9:07 dpdklab
2023-11-28 9:03 dpdklab
2023-11-28 9:02 dpdklab
2023-11-28 9:01 dpdklab
2023-11-28 8:59 dpdklab
2023-11-28 8:58 dpdklab
2023-11-28 8:57 dpdklab
2023-11-28 8:54 dpdklab
2023-11-28 8:54 dpdklab
2023-11-28 8:53 dpdklab
2023-11-28 8:52 dpdklab
2023-11-28 8:51 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=6565bf22.050a0220.657f9.f62bSMTPIN_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).