From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137208-137210 [PATCH] [v7,3/3] net/mlx5/hws: add compare
Date: Mon, 26 Feb 2024 12:39:14 -0800 (PST) [thread overview]
Message-ID: <65dcf6f2.170a0220.5eacc.06f0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137210
_Testing PASS_
Submitter: Michael Baum <michaelba@nvidia.com>
Date: Monday, February 26 2024 13:18:48
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:812898e35f0d21c18d5fae3261873661258abd83
137208-137210 --> testing pass
Test environment and result as below:
+--------------------------+----------------+--------------+
| Environment | dpdk_unit_test | lpm_autotest |
+==========================+================+==============+
| CentOS Stream 9 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+--------------+
| Debian 11 (Buster) (ARM) | PASS | SKIPPED |
+--------------------------+----------------+--------------+
| Fedora 37 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | PASS |
+--------------------------+----------------+--------------+
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29265/
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-26 20:39 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 20:39 dpdklab [this message]
[not found] <20240226131848.2982242-4-michaelba@nvidia.com>
2024-02-28 3:54 ` dpdklab
2024-02-28 4:01 ` dpdklab
2024-02-28 4:03 ` dpdklab
2024-02-28 4:05 ` dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-02-27 3:16 dpdklab
2024-02-26 23:30 dpdklab
2024-02-26 21:30 dpdklab
2024-02-26 21:27 dpdklab
2024-02-26 21:23 dpdklab
2024-02-26 21:20 dpdklab
2024-02-26 21:19 dpdklab
2024-02-26 21:14 dpdklab
2024-02-26 21:12 dpdklab
2024-02-26 21:11 dpdklab
2024-02-26 20:56 dpdklab
2024-02-26 20:56 dpdklab
2024-02-26 20:56 dpdklab
2024-02-26 20:46 dpdklab
2024-02-26 20:44 dpdklab
2024-02-26 20:41 dpdklab
2024-02-26 20:39 dpdklab
2024-02-26 20:36 dpdklab
2024-02-26 20:35 dpdklab
2024-02-26 20:34 dpdklab
2024-02-26 20:34 dpdklab
2024-02-26 20:33 dpdklab
2024-02-26 20:32 dpdklab
2024-02-26 20:31 dpdklab
2024-02-26 20:30 dpdklab
2024-02-26 20:29 dpdklab
2024-02-26 20:29 dpdklab
2024-02-26 20:28 dpdklab
2024-02-26 20:27 dpdklab
2024-02-26 20:27 dpdklab
2024-02-26 20:27 dpdklab
2024-02-26 20:26 dpdklab
2024-02-26 20:26 dpdklab
2024-02-26 20:25 dpdklab
2024-02-26 20:24 dpdklab
2024-02-26 20:24 dpdklab
2024-02-26 20:24 dpdklab
2024-02-26 20:23 dpdklab
2024-02-26 20:22 dpdklab
2024-02-26 20:21 dpdklab
2024-02-26 20:19 dpdklab
2024-02-26 20:17 dpdklab
2024-02-26 20:15 dpdklab
2024-02-26 20:15 dpdklab
2024-02-26 20:14 dpdklab
2024-02-26 20:10 dpdklab
2024-02-26 20:09 dpdklab
2024-02-26 20:09 dpdklab
2024-02-26 20:08 dpdklab
2024-02-26 20:07 dpdklab
2024-02-26 20:07 dpdklab
2024-02-26 20:06 dpdklab
2024-02-26 20:06 dpdklab
2024-02-26 20:06 dpdklab
2024-02-26 20:00 dpdklab
2024-02-26 19:56 dpdklab
2024-02-26 19:55 dpdklab
2024-02-26 19:54 dpdklab
2024-02-26 19:54 dpdklab
2024-02-26 19:52 dpdklab
2024-02-26 19:49 dpdklab
2024-02-26 19:47 dpdklab
2024-02-26 19:47 dpdklab
2024-02-26 19:44 dpdklab
2024-02-26 19:42 dpdklab
2024-02-26 19:38 dpdklab
2024-02-26 19:35 dpdklab
2024-02-26 19:35 dpdklab
2024-02-26 19:34 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=65dcf6f2.170a0220.5eacc.06f0SMTPIN_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).