From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135750 [PATCH] common/cnxk: update MACsec pkt ok count
Date: Fri, 05 Jan 2024 12:27:07 -0800 (PST) [thread overview]
Message-ID: <6598661b.050a0220.3122a.503aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135750
_Testing PASS_
Submitter: Akhil Goyal <gakhil@marvell.com>
Date: Friday, January 05 2024 09:15:16
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871
135750 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
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/28802/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-05 20:27 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 20:27 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-06 3:50 dpdklab
2024-01-06 1:32 dpdklab
2024-01-06 0:32 dpdklab
2024-01-05 23:58 dpdklab
2024-01-05 23:38 dpdklab
2024-01-05 22:55 dpdklab
2024-01-05 22:53 dpdklab
2024-01-05 22:52 dpdklab
2024-01-05 22:38 dpdklab
2024-01-05 22:37 dpdklab
2024-01-05 22:34 dpdklab
2024-01-05 22:34 dpdklab
2024-01-05 22:34 dpdklab
2024-01-05 22:33 dpdklab
2024-01-05 22:33 dpdklab
2024-01-05 22:33 dpdklab
2024-01-05 22:32 dpdklab
2024-01-05 22:32 dpdklab
2024-01-05 22:31 dpdklab
2024-01-05 22:31 dpdklab
2024-01-05 22:30 dpdklab
2024-01-05 22:30 dpdklab
2024-01-05 22:29 dpdklab
2024-01-05 22:27 dpdklab
2024-01-05 22:27 dpdklab
2024-01-05 22:26 dpdklab
2024-01-05 22:26 dpdklab
2024-01-05 22:26 dpdklab
2024-01-05 22:26 dpdklab
2024-01-05 22:22 dpdklab
2024-01-05 22:19 dpdklab
2024-01-05 22:15 dpdklab
2024-01-05 22:13 dpdklab
2024-01-05 22:10 dpdklab
2024-01-05 22:08 dpdklab
2024-01-05 22:08 dpdklab
2024-01-05 22:07 dpdklab
2024-01-05 21:58 dpdklab
2024-01-05 21:57 dpdklab
2024-01-05 21:55 dpdklab
2024-01-05 21:53 dpdklab
2024-01-05 21:47 dpdklab
2024-01-05 21:43 dpdklab
2024-01-05 21:42 dpdklab
2024-01-05 21:38 dpdklab
2024-01-05 21:38 dpdklab
2024-01-05 21:35 dpdklab
2024-01-05 21:34 dpdklab
2024-01-05 21:34 dpdklab
2024-01-05 21:33 dpdklab
2024-01-05 21:32 dpdklab
2024-01-05 21:28 dpdklab
2024-01-05 21:28 dpdklab
2024-01-05 21:27 dpdklab
2024-01-05 21:22 dpdklab
2024-01-05 21:17 dpdklab
2024-01-05 21:09 dpdklab
2024-01-05 20:58 dpdklab
2024-01-05 20:27 dpdklab
2024-01-05 20:21 dpdklab
2024-01-05 20:18 dpdklab
2024-01-05 20:07 dpdklab
2024-01-05 20:01 dpdklab
2024-01-05 19:54 dpdklab
2024-01-05 19:53 dpdklab
2024-01-05 19:49 dpdklab
2024-01-05 19:46 dpdklab
2024-01-05 19:46 dpdklab
[not found] <20240105091516.2508910-1-gakhil@marvell.com>
2024-01-05 8:57 ` qemudev
2024-01-05 9:01 ` qemudev
2024-01-05 9:15 ` checkpatch
2024-01-05 10:05 ` 0-day Robot
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=6598661b.050a0220.3122a.503aSMTPIN_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).