From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136284 [PATCH] [v2] app/testpmd: command to get descript
Date: Thu, 01 Feb 2024 08:34:41 -0800 (PST) [thread overview]
Message-ID: <65bbc821.050a0220.dea44.00b9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136284
_Testing PASS_
Submitter: Satha Koteswara Rao Kottidi <skoteshwar@marvell.com>
Date: Thursday, February 01 2024 13:52:42
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:1d14e0581427004de88ac95e25529761f4492621
136284 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29018/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-01 16:34 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 16:34 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-01 19:36 dpdklab
2024-02-01 19:01 dpdklab
2024-02-01 17:53 dpdklab
2024-02-01 17:48 dpdklab
2024-02-01 17:41 dpdklab
2024-02-01 17:37 dpdklab
2024-02-01 17:31 dpdklab
2024-02-01 17:28 dpdklab
2024-02-01 17:28 dpdklab
2024-02-01 17:25 dpdklab
2024-02-01 17:22 dpdklab
2024-02-01 17:20 dpdklab
2024-02-01 17:19 dpdklab
2024-02-01 17:18 dpdklab
2024-02-01 17:17 dpdklab
2024-02-01 17:16 dpdklab
2024-02-01 17:09 dpdklab
2024-02-01 17:08 dpdklab
2024-02-01 17:07 dpdklab
2024-02-01 17:07 dpdklab
2024-02-01 17:07 dpdklab
2024-02-01 17:06 dpdklab
2024-02-01 17:06 dpdklab
2024-02-01 17:02 dpdklab
2024-02-01 17:00 dpdklab
2024-02-01 17:00 dpdklab
2024-02-01 16:59 dpdklab
2024-02-01 16:59 dpdklab
2024-02-01 16:59 dpdklab
2024-02-01 16:58 dpdklab
2024-02-01 16:56 dpdklab
2024-02-01 16:55 dpdklab
2024-02-01 16:54 dpdklab
2024-02-01 16:54 dpdklab
2024-02-01 16:53 dpdklab
2024-02-01 16:53 dpdklab
2024-02-01 16:51 dpdklab
2024-02-01 16:51 dpdklab
2024-02-01 16:51 dpdklab
2024-02-01 16:50 dpdklab
2024-02-01 16:49 dpdklab
2024-02-01 16:46 dpdklab
2024-02-01 16:46 dpdklab
2024-02-01 16:46 dpdklab
2024-02-01 16:46 dpdklab
2024-02-01 16:45 dpdklab
2024-02-01 16:44 dpdklab
2024-02-01 16:44 dpdklab
2024-02-01 16:44 dpdklab
2024-02-01 16:44 dpdklab
2024-02-01 16:43 dpdklab
2024-02-01 16:41 dpdklab
2024-02-01 16:41 dpdklab
2024-02-01 16:40 dpdklab
2024-02-01 16:38 dpdklab
2024-02-01 16:38 dpdklab
2024-02-01 16:37 dpdklab
2024-02-01 16:37 dpdklab
2024-02-01 16:37 dpdklab
2024-02-01 16:35 dpdklab
2024-02-01 16:35 dpdklab
2024-02-01 16:35 dpdklab
2024-02-01 16:35 dpdklab
2024-02-01 16:34 dpdklab
2024-02-01 16:34 dpdklab
2024-02-01 16:34 dpdklab
2024-02-01 16:34 dpdklab
2024-02-01 16:33 dpdklab
2024-02-01 16: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=65bbc821.050a0220.dea44.00b9SMTPIN_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).