From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136257-136259 [PATCH] [v5,3/3] net/mlx5: add compare ite
Date: Thu, 01 Feb 2024 05:01:04 -0800 (PST) [thread overview]
Message-ID: <65bb9610.d40a0220.1256a.d381SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136259
_Testing PASS_
Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: Thursday, February 01 2024 12:29:22
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:8e5cbd3d1f6f077abdcb2ef4de027603ba9af5ca
136257-136259 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29015/
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-01 13:01 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 13:01 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-01 15:09 dpdklab
2024-02-01 14:35 dpdklab
2024-02-01 14:24 dpdklab
2024-02-01 14:22 dpdklab
2024-02-01 14:17 dpdklab
2024-02-01 14:17 dpdklab
2024-02-01 14:16 dpdklab
2024-02-01 14:15 dpdklab
2024-02-01 14:01 dpdklab
2024-02-01 14:00 dpdklab
2024-02-01 13:58 dpdklab
2024-02-01 13:57 dpdklab
2024-02-01 13:56 dpdklab
2024-02-01 13:56 dpdklab
2024-02-01 13:55 dpdklab
2024-02-01 13:54 dpdklab
2024-02-01 13:54 dpdklab
2024-02-01 13:54 dpdklab
2024-02-01 13:52 dpdklab
2024-02-01 13:51 dpdklab
2024-02-01 13:48 dpdklab
2024-02-01 13:48 dpdklab
2024-02-01 13:47 dpdklab
2024-02-01 13:46 dpdklab
2024-02-01 13:46 dpdklab
2024-02-01 13:46 dpdklab
2024-02-01 13:45 dpdklab
2024-02-01 13:45 dpdklab
2024-02-01 13:44 dpdklab
2024-02-01 13:39 dpdklab
2024-02-01 13:39 dpdklab
2024-02-01 13:38 dpdklab
2024-02-01 13:38 dpdklab
2024-02-01 13:35 dpdklab
2024-02-01 13:33 dpdklab
2024-02-01 13:25 dpdklab
2024-02-01 13:25 dpdklab
2024-02-01 13:25 dpdklab
2024-02-01 13:24 dpdklab
2024-02-01 13:24 dpdklab
2024-02-01 13:22 dpdklab
2024-02-01 13:22 dpdklab
2024-02-01 13:22 dpdklab
2024-02-01 13:22 dpdklab
2024-02-01 13:21 dpdklab
2024-02-01 13:21 dpdklab
2024-02-01 13:21 dpdklab
2024-02-01 13:21 dpdklab
2024-02-01 13:15 dpdklab
2024-02-01 13:14 dpdklab
2024-02-01 13:13 dpdklab
2024-02-01 13:13 dpdklab
2024-02-01 13:13 dpdklab
2024-02-01 13:13 dpdklab
2024-02-01 13:10 dpdklab
2024-02-01 13:10 dpdklab
2024-02-01 13:09 dpdklab
2024-02-01 13:09 dpdklab
2024-02-01 13:08 dpdklab
2024-02-01 13:07 dpdklab
2024-02-01 13:07 dpdklab
2024-02-01 13:02 dpdklab
2024-02-01 13:02 dpdklab
2024-02-01 13:02 dpdklab
2024-02-01 13:01 dpdklab
2024-02-01 13:01 dpdklab
2024-02-01 13:00 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=65bb9610.d40a0220.1256a.d381SMTPIN_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).