From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw131985 [PATCH] [v4] app/test: append 'allow' parameters
Date: Wed, 27 Sep 2023 00:27:13 -0700 (PDT) [thread overview]
Message-ID: <6513d951.170a0220.b9ba2.bf8fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/131985
_Testing PASS_
Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Wednesday, September 27 2023 03:42:04
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d58c97481a136ad5342c9d8717b22bdaa5eccd43
131985 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27743/
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-27 7:27 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 7:27 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-27 13:52 dpdklab
2023-09-27 9:12 dpdklab
2023-09-27 8:58 dpdklab
2023-09-27 8:52 dpdklab
2023-09-27 8:47 dpdklab
2023-09-27 8:44 dpdklab
2023-09-27 8:29 dpdklab
2023-09-27 8:28 dpdklab
2023-09-27 8:25 dpdklab
2023-09-27 8:20 dpdklab
2023-09-27 8:13 dpdklab
2023-09-27 8:11 dpdklab
2023-09-27 8:09 dpdklab
2023-09-27 8:09 dpdklab
2023-09-27 8:07 dpdklab
2023-09-27 8:05 dpdklab
2023-09-27 8:03 dpdklab
2023-09-27 8:00 dpdklab
2023-09-27 8:00 dpdklab
2023-09-27 7:55 dpdklab
2023-09-27 7:55 dpdklab
2023-09-27 7:53 dpdklab
2023-09-27 7:53 dpdklab
2023-09-27 7:51 dpdklab
2023-09-27 7:49 dpdklab
2023-09-27 7:48 dpdklab
2023-09-27 7:47 dpdklab
2023-09-27 7:47 dpdklab
2023-09-27 7:46 dpdklab
2023-09-27 7:45 dpdklab
2023-09-27 7:40 dpdklab
2023-09-27 7:38 dpdklab
2023-09-27 5:17 dpdklab
2023-09-27 5:10 dpdklab
2023-09-27 5:05 dpdklab
2023-09-27 5:03 dpdklab
2023-09-27 5:00 dpdklab
2023-09-27 5:00 dpdklab
2023-09-27 4:59 dpdklab
2023-09-27 4:53 dpdklab
2023-09-27 4:53 dpdklab
2023-09-27 4:49 dpdklab
2023-09-27 4:44 dpdklab
2023-09-27 4:43 dpdklab
2023-09-27 4:40 dpdklab
2023-09-27 4:38 dpdklab
2023-09-27 4:37 dpdklab
2023-09-27 4:35 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=6513d951.170a0220.b9ba2.bf8fSMTPIN_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).