From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Qi Zhang <qi.z.zhang@intel.com>
Subject: |SUCCESS| pw132087-132095 [PATCH] [v9,9/9] net/cpfl: add support of
Date: Thu, 28 Sep 2023 06:38:57 -0700 (PDT) [thread overview]
Message-ID: <651581f1.9f0a0220.911d8.216eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132095
_Testing PASS_
Submitter: Zhang, Yuying <yuying.zhang@intel.com>
Date: Thursday, September 28 2023 08:44:58
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: master
CommitID:4a343f542828a6c41edb473718dbb55b43f84dbe
132087-132095 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
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/27762/
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-28 13:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 13:38 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-28 16:25 dpdklab
2023-09-28 14:43 dpdklab
2023-09-28 14:35 dpdklab
2023-09-28 13:30 dpdklab
2023-09-28 13:30 dpdklab
2023-09-28 13:26 dpdklab
2023-09-28 13:11 dpdklab
2023-09-28 13:10 dpdklab
2023-09-28 13:09 dpdklab
2023-09-28 13:07 dpdklab
2023-09-28 13:07 dpdklab
2023-09-28 13:07 dpdklab
2023-09-28 13:05 dpdklab
2023-09-28 13:05 dpdklab
2023-09-28 13:03 dpdklab
2023-09-28 13:02 dpdklab
2023-09-28 13:01 dpdklab
2023-09-28 13:01 dpdklab
2023-09-28 13:00 dpdklab
2023-09-28 13:00 dpdklab
2023-09-28 13:00 dpdklab
2023-09-28 12:50 dpdklab
2023-09-28 12:50 dpdklab
2023-09-28 12:29 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=651581f1.9f0a0220.911d8.216eSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=qi.z.zhang@intel.com \
--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).