From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135877 [PATCH] net/mlx5/hws: fix ESP matching validation
Date: Mon, 15 Jan 2024 05:44:09 -0800 (PST) [thread overview]
Message-ID: <65a536a9.050a0220.a91ad.f2f8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135877
_Testing PASS_
Submitter: Michael Baum <michaelba@nvidia.com>
Date: Monday, January 15 2024 12:09:39
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:30468d404a3447cae8797576e885b9831bb88391
135877 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28865/
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-15 13:44 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 13:44 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-16 18:51 dpdklab
2024-01-15 14:55 dpdklab
2024-01-15 14:55 dpdklab
2024-01-15 14:42 dpdklab
2024-01-15 14:32 dpdklab
2024-01-15 14:28 dpdklab
2024-01-15 14:26 dpdklab
2024-01-15 14:26 dpdklab
2024-01-15 14:23 dpdklab
2024-01-15 14:22 dpdklab
2024-01-15 14:21 dpdklab
2024-01-15 14:20 dpdklab
2024-01-15 14:20 dpdklab
2024-01-15 14:19 dpdklab
2024-01-15 14:17 dpdklab
2024-01-15 14:16 dpdklab
2024-01-15 14:15 dpdklab
2024-01-15 14:15 dpdklab
2024-01-15 14:14 dpdklab
2024-01-15 14:13 dpdklab
2024-01-15 14:13 dpdklab
2024-01-15 14:13 dpdklab
2024-01-15 14:12 dpdklab
2024-01-15 14:11 dpdklab
2024-01-15 14:08 dpdklab
2024-01-15 14:08 dpdklab
2024-01-15 14:07 dpdklab
2024-01-15 14:06 dpdklab
2024-01-15 14:03 dpdklab
2024-01-15 14:02 dpdklab
2024-01-15 14:01 dpdklab
2024-01-15 13:58 dpdklab
2024-01-15 13:57 dpdklab
2024-01-15 13:53 dpdklab
2024-01-15 13:53 dpdklab
2024-01-15 13:53 dpdklab
2024-01-15 13:53 dpdklab
2024-01-15 13:52 dpdklab
2024-01-15 13:52 dpdklab
2024-01-15 13:52 dpdklab
2024-01-15 13:52 dpdklab
2024-01-15 13:51 dpdklab
2024-01-15 13:51 dpdklab
2024-01-15 13:51 dpdklab
2024-01-15 13:50 dpdklab
2024-01-15 13:50 dpdklab
2024-01-15 13:49 dpdklab
2024-01-15 13:49 dpdklab
2024-01-15 13:49 dpdklab
2024-01-15 13:48 dpdklab
2024-01-15 13:47 dpdklab
2024-01-15 13:47 dpdklab
2024-01-15 13:47 dpdklab
2024-01-15 13:46 dpdklab
2024-01-15 13:46 dpdklab
2024-01-15 13:46 dpdklab
2024-01-15 13:45 dpdklab
2024-01-15 13:43 dpdklab
2024-01-15 13:42 dpdklab
2024-01-15 13:42 dpdklab
2024-01-15 13:41 dpdklab
2024-01-15 13:40 dpdklab
2024-01-15 13:39 dpdklab
2024-01-15 13:39 dpdklab
2024-01-15 13:37 dpdklab
2024-01-15 13:30 dpdklab
2024-01-15 13:21 dpdklab
2024-01-15 13:21 dpdklab
2024-01-15 13:19 dpdklab
2024-01-15 13:16 dpdklab
[not found] <20240115120938.3994588-1-michaelba@nvidia.com>
2024-01-15 11:48 ` qemudev
2024-01-15 11:52 ` qemudev
2024-01-15 12:10 ` checkpatch
2024-01-15 12:43 ` 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=65a536a9.050a0220.a91ad.f2f8SMTPIN_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).