From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136623-136631 [PATCH] [9/9] net/mlx5/hws: support push_e
Date: Tue, 13 Feb 2024 03:23:52 -0800 (PST) [thread overview]
Message-ID: <65cb5148.050a0220.29e99.78a5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136631
_Testing PASS_
Submitter: Itamar Gozlan <igozlan@nvidia.com>
Date: Tuesday, February 13 2024 09:50:37
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b9e20153ea808f12d89090655096c78b1918fc0e
136623-136631 --> 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 |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Buster | 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)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29125/
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-13 11:23 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 11:23 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-13 12:40 dpdklab
2024-02-13 12:39 dpdklab
2024-02-13 12:38 dpdklab
2024-02-13 12:23 dpdklab
2024-02-13 12:21 dpdklab
2024-02-13 12:05 dpdklab
2024-02-13 12:05 dpdklab
2024-02-13 12:05 dpdklab
2024-02-13 12:03 dpdklab
2024-02-13 12:01 dpdklab
2024-02-13 12:00 dpdklab
2024-02-13 12:00 dpdklab
2024-02-13 12:00 dpdklab
2024-02-13 11:58 dpdklab
2024-02-13 11:57 dpdklab
2024-02-13 11:57 dpdklab
2024-02-13 11:56 dpdklab
2024-02-13 11:51 dpdklab
2024-02-13 11:43 dpdklab
2024-02-13 11:39 dpdklab
2024-02-13 11:39 dpdklab
2024-02-13 11:38 dpdklab
2024-02-13 11:38 dpdklab
2024-02-13 11:38 dpdklab
2024-02-13 11:38 dpdklab
2024-02-13 11:38 dpdklab
2024-02-13 11:37 dpdklab
2024-02-13 11:37 dpdklab
2024-02-13 11:37 dpdklab
2024-02-13 11:37 dpdklab
2024-02-13 11:36 dpdklab
2024-02-13 11:36 dpdklab
2024-02-13 11:35 dpdklab
2024-02-13 11:35 dpdklab
2024-02-13 11:35 dpdklab
2024-02-13 11:34 dpdklab
2024-02-13 11:34 dpdklab
2024-02-13 11:34 dpdklab
2024-02-13 11:33 dpdklab
2024-02-13 11:33 dpdklab
2024-02-13 11:32 dpdklab
2024-02-13 11:32 dpdklab
2024-02-13 11:32 dpdklab
2024-02-13 11:31 dpdklab
2024-02-13 11:31 dpdklab
2024-02-13 11:30 dpdklab
2024-02-13 11:30 dpdklab
2024-02-13 11:29 dpdklab
2024-02-13 11:29 dpdklab
2024-02-13 11:29 dpdklab
2024-02-13 11:28 dpdklab
2024-02-13 11:28 dpdklab
2024-02-13 11:28 dpdklab
2024-02-13 11:27 dpdklab
2024-02-13 11:27 dpdklab
2024-02-13 11:26 dpdklab
2024-02-13 11:26 dpdklab
2024-02-13 11:25 dpdklab
2024-02-13 11:24 dpdklab
2024-02-13 11:24 dpdklab
2024-02-13 11:24 dpdklab
2024-02-13 11:22 dpdklab
2024-02-13 11:21 dpdklab
2024-02-13 11:21 dpdklab
2024-02-13 11:05 dpdklab
2024-02-13 10:58 dpdklab
2024-02-13 10:57 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=65cb5148.050a0220.29e99.78a5SMTPIN_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).