From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139031-139034 [PATCH] [v9,4/4] cryptodev: remove rte mar
Date: Tue, 02 Apr 2024 14:03:31 -0700 (PDT) [thread overview]
Message-ID: <660c72a3.050a0220.9d0b.05adSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1712088530-24948-5-git-send-email-roretzla@linux.microsoft.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139034
_Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tuesday, April 02 2024 20:08:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139031-139034 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29694/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-04-02 21:03 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1712088530-24948-5-git-send-email-roretzla@linux.microsoft.com>
2024-04-02 19:46 ` |SUCCESS| pw139031-139034 [PATCH v9 4/4] cryptodev: remove rte marker fields qemudev
2024-04-02 19:51 ` qemudev
2024-04-02 20:11 ` |WARNING| pw139034 " checkpatch
2024-04-02 20:44 ` |SUCCESS| pw139031-139034 [PATCH] [v9,4/4] cryptodev: remove rte mar dpdklab
2024-04-02 20:44 ` dpdklab
2024-04-02 20:45 ` dpdklab
2024-04-02 20:45 ` dpdklab
2024-04-02 20:45 ` dpdklab
2024-04-02 20:45 ` dpdklab
2024-04-02 20:45 ` dpdklab
2024-04-02 20:46 ` dpdklab
2024-04-02 20:46 ` dpdklab
2024-04-02 20:46 ` dpdklab
2024-04-02 20:48 ` dpdklab
2024-04-02 20:48 ` dpdklab
2024-04-02 20:49 ` dpdklab
2024-04-02 20:50 ` dpdklab
2024-04-02 20:51 ` |WARNING| " dpdklab
2024-04-02 20:53 ` dpdklab
2024-04-02 20:55 ` |SUCCESS| " dpdklab
2024-04-02 20:56 ` dpdklab
2024-04-02 20:57 ` dpdklab
2024-04-02 20:57 ` |WARNING| " dpdklab
2024-04-02 20:59 ` |SUCCESS| " dpdklab
2024-04-02 21:00 ` |WARNING| " dpdklab
2024-04-02 21:00 ` dpdklab
2024-04-02 21:01 ` |SUCCESS| " dpdklab
2024-04-02 21:01 ` |WARNING| " dpdklab
2024-04-02 21:01 ` dpdklab
2024-04-02 21:02 ` |SUCCESS| " dpdklab
2024-04-02 21:02 ` |WARNING| " dpdklab
2024-04-02 21:02 ` dpdklab
2024-04-02 21:03 ` dpdklab [this message]
2024-04-02 21:03 ` |SUCCESS| " dpdklab
2024-04-02 21:05 ` |SUCCESS| pw139034 [PATCH v9 4/4] cryptodev: remove rte marker fields 0-day Robot
2024-04-02 21:09 ` |WARNING| pw139031-139034 [PATCH] [v9,4/4] cryptodev: remove rte mar dpdklab
2024-04-02 21:10 ` dpdklab
2024-04-02 21:12 ` |SUCCESS| " dpdklab
2024-04-02 21:12 ` dpdklab
2024-04-02 21:12 ` dpdklab
2024-04-02 21:20 ` dpdklab
2024-04-02 21:20 ` dpdklab
2024-04-02 21:21 ` dpdklab
2024-04-02 21:23 ` dpdklab
2024-04-02 21:23 ` dpdklab
2024-04-02 21:23 ` dpdklab
2024-04-02 21:23 ` dpdklab
2024-04-02 21:25 ` dpdklab
2024-04-02 21:25 ` dpdklab
2024-04-02 21:26 ` dpdklab
2024-04-02 21:26 ` |WARNING| " dpdklab
2024-04-02 21:28 ` |SUCCESS| " dpdklab
2024-04-02 21:28 ` dpdklab
2024-04-02 21:29 ` dpdklab
2024-04-02 21:30 ` dpdklab
2024-04-02 21:32 ` dpdklab
2024-04-02 21:33 ` dpdklab
2024-04-02 21:35 ` dpdklab
2024-04-02 21:35 ` dpdklab
2024-04-02 21:37 ` dpdklab
2024-04-02 21:48 ` dpdklab
2024-04-02 21:55 ` |FAILURE| " dpdklab
2024-04-02 21:55 ` |SUCCESS| " dpdklab
2024-04-02 21:57 ` dpdklab
2024-04-02 21:57 ` dpdklab
2024-04-02 21:57 ` dpdklab
2024-04-02 21:58 ` |FAILURE| " dpdklab
2024-04-02 21:59 ` |SUCCESS| " dpdklab
2024-04-02 21:59 ` |FAILURE| " dpdklab
2024-04-02 22:04 ` dpdklab
2024-04-02 22:20 ` |SUCCESS| " dpdklab
2024-04-02 22:20 ` dpdklab
2024-04-02 22:21 ` |FAILURE| " dpdklab
2024-04-02 22:21 ` |SUCCESS| " dpdklab
2024-04-02 22:23 ` dpdklab
2024-04-02 22:24 ` dpdklab
2024-04-02 22:24 ` |FAILURE| " dpdklab
2024-04-02 22:26 ` dpdklab
2024-04-02 22:26 ` dpdklab
2024-04-02 22:27 ` |SUCCESS| " dpdklab
2024-04-02 22:27 ` |FAILURE| " dpdklab
2024-04-02 22:28 ` |SUCCESS| " dpdklab
2024-04-02 22:30 ` |FAILURE| " dpdklab
2024-04-02 22:39 ` |SUCCESS| " dpdklab
2024-04-02 23:38 ` dpdklab
2024-04-03 0:02 ` dpdklab
2024-04-03 19:55 ` dpdklab
2024-04-03 19:57 ` dpdklab
2024-04-03 20:13 ` dpdklab
2024-04-03 20:17 ` dpdklab
2024-04-03 20:22 ` 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=660c72a3.050a0220.9d0b.05adSMTPIN_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).