From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129966-129994 [PATCH] [v2,29/29] port: make API's stable
Date: Tue, 08 Aug 2023 18:25:31 -0700 (PDT) [thread overview]
Message-ID: <64d2eb0b.0d0a0220.a5662.4424SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-x86_64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/129994
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, August 09 2023 00:10:17
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:9836014d4c2b1b2c29948c928fd386b2944b6bcf
129966-129994 --> 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/27254/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-09 1:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 1:25 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-09 8:23 dpdklab
2023-08-09 8:15 dpdklab
2023-08-09 8:11 dpdklab
2023-08-09 7:51 dpdklab
2023-08-09 7:39 dpdklab
2023-08-09 2:17 dpdklab
2023-08-09 1:45 dpdklab
2023-08-09 1:23 dpdklab
2023-08-09 1:21 dpdklab
2023-08-09 1:21 dpdklab
2023-08-09 1:20 dpdklab
2023-08-09 1:09 dpdklab
2023-08-09 0:59 dpdklab
2023-08-09 0:58 dpdklab
2023-08-09 0:52 dpdklab
2023-08-09 0:49 dpdklab
2023-08-09 0:47 dpdklab
2023-08-09 0:46 dpdklab
[not found] <20230809001017.293037-30-stephen@networkplumber.org>
2023-08-09 0:02 ` |SUCCESS| pw129966-129994 [PATCH v2 29/29] " qemudev
2023-08-09 0:06 ` qemudev
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=64d2eb0b.0d0a0220.a5662.4424SMTPIN_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).