From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw131143-131140 [PATCH] [5/5] app/proc-info: support query
Date: Mon, 04 Sep 2023 05:18:45 -0700 (PDT) [thread overview]
Message-ID: <64f5cb25.920a0220.d5e7e.258dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/131140
_Testing PASS_
Submitter: Jie Hai <haijie1@huawei.com>
Date: Monday, September 04 2023 07:28:51
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:799d56f1192d72872e63fbb3d2c7f776b7ae89b0
131143-131140 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27514/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-04 12:18 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 12:18 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-06 2:00 dpdklab
2023-09-06 1:49 dpdklab
2023-09-06 1:44 dpdklab
2023-09-06 1:39 dpdklab
2023-09-05 15:40 dpdklab
2023-09-05 15:37 dpdklab
2023-09-05 15:34 dpdklab
2023-09-05 2:24 dpdklab
2023-09-05 2:18 dpdklab
2023-09-04 13:24 dpdklab
2023-09-04 13:03 dpdklab
2023-09-04 13:02 dpdklab
2023-09-04 13:00 dpdklab
2023-09-04 12:59 dpdklab
2023-09-04 12:57 dpdklab
2023-09-04 12:57 dpdklab
2023-09-04 12:52 dpdklab
2023-09-04 12:51 dpdklab
2023-09-04 12:47 dpdklab
2023-09-04 12:46 dpdklab
2023-09-04 12:45 dpdklab
2023-09-04 12:44 dpdklab
2023-09-04 12:40 dpdklab
2023-09-04 12:39 dpdklab
2023-09-04 12:36 dpdklab
2023-09-04 12:35 dpdklab
2023-09-04 12:33 dpdklab
2023-09-04 12:32 dpdklab
2023-09-04 12:32 dpdklab
2023-09-04 12:32 dpdklab
2023-09-04 12:32 dpdklab
2023-09-04 12:31 dpdklab
2023-09-04 12:30 dpdklab
2023-09-04 12:27 dpdklab
2023-09-04 12:26 dpdklab
2023-09-04 12:24 dpdklab
2023-09-04 12:22 dpdklab
2023-09-04 12:18 dpdklab
2023-09-04 12:16 dpdklab
2023-09-04 12:12 dpdklab
2023-09-04 12:03 dpdklab
2023-09-04 11:38 dpdklab
2023-09-04 11:28 dpdklab
2023-09-04 11:27 dpdklab
2023-09-04 11:19 dpdklab
2023-09-04 11:09 dpdklab
2023-09-04 11:04 dpdklab
2023-09-04 11:04 dpdklab
2023-09-04 11:04 dpdklab
2023-09-04 11:02 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=64f5cb25.920a0220.d5e7e.258dSMTPIN_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).