From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136746-136748 [PATCH] [v5,3/3] net/mlx5/hws: add compare
Date: Wed, 14 Feb 2024 06:01:33 -0800 (PST) [thread overview]
Message-ID: <65ccc7bd.050a0220.9b651.c1cbSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136748
_Testing PASS_
Submitter: Michael Baum <michaelba@nvidia.com>
Date: Wednesday, February 14 2024 07:30:15
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:32bedd138f36b073341bbde2a5186727d1bc05d6
136746-136748 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Fedora 37 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29146/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-14 14:01 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 14:01 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-14 19:36 dpdklab
2024-02-14 19:02 dpdklab
2024-02-14 17:53 dpdklab
2024-02-14 17:25 dpdklab
2024-02-14 17:06 dpdklab
2024-02-14 15:02 dpdklab
2024-02-14 15:02 dpdklab
2024-02-14 14:51 dpdklab
2024-02-14 14:48 dpdklab
2024-02-14 14:45 dpdklab
2024-02-14 14:44 dpdklab
2024-02-14 14:43 dpdklab
2024-02-14 14:40 dpdklab
2024-02-14 14:39 dpdklab
2024-02-14 14:39 dpdklab
2024-02-14 14:38 dpdklab
2024-02-14 14:37 dpdklab
2024-02-14 14:35 dpdklab
2024-02-14 14:35 dpdklab
2024-02-14 14:33 dpdklab
2024-02-14 14:32 dpdklab
2024-02-14 14:29 dpdklab
2024-02-14 14:25 dpdklab
2024-02-14 14:25 dpdklab
2024-02-14 14:20 dpdklab
2024-02-14 14:19 dpdklab
2024-02-14 14:19 dpdklab
2024-02-14 14:18 dpdklab
2024-02-14 14:14 dpdklab
2024-02-14 14:14 dpdklab
2024-02-14 14:12 dpdklab
2024-02-14 14:12 dpdklab
2024-02-14 14:12 dpdklab
2024-02-14 14:12 dpdklab
2024-02-14 14:10 dpdklab
2024-02-14 14:10 dpdklab
2024-02-14 14:08 dpdklab
2024-02-14 14:07 dpdklab
2024-02-14 14:06 dpdklab
2024-02-14 14:05 dpdklab
2024-02-14 14:05 dpdklab
2024-02-14 14:04 dpdklab
2024-02-14 14:04 dpdklab
2024-02-14 14:04 dpdklab
2024-02-14 14:01 dpdklab
2024-02-14 14:01 dpdklab
2024-02-14 13:59 dpdklab
2024-02-14 13:59 dpdklab
2024-02-14 13:57 dpdklab
2024-02-14 13:55 dpdklab
2024-02-14 13:53 dpdklab
2024-02-14 13:52 dpdklab
2024-02-14 13:51 dpdklab
2024-02-14 13:49 dpdklab
2024-02-14 13:49 dpdklab
2024-02-14 13:47 dpdklab
2024-02-14 13:45 dpdklab
2024-02-14 13:36 dpdklab
2024-02-14 13:34 dpdklab
2024-02-14 13:34 dpdklab
2024-02-14 13:34 dpdklab
2024-02-14 13:34 dpdklab
2024-02-14 13:32 dpdklab
2024-02-14 13:32 dpdklab
2024-02-14 13:31 dpdklab
2024-02-14 13:25 dpdklab
2024-02-14 13:25 dpdklab
2024-02-14 13:24 dpdklab
2024-02-14 13:24 dpdklab
2024-02-14 13:24 dpdklab
2024-02-14 13:23 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=65ccc7bd.050a0220.9b651.c1cbSMTPIN_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).