automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Shun Hao <shunh@nvidia.com>
Subject: |SUCCESS| pw132140-132142 [PATCH] [v1,3/3] net/mlx5/hws: add support
Date: Thu, 28 Sep 2023 13:00:28 -0700 (PDT)	[thread overview]
Message-ID: <6515db5c.810a0220.270f8.fa0fSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132142

_Testing PASS_

Submitter: Shun Hao <shunh@nvidia.com>
Date: Thursday, September 28 2023 13:09:13 
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: master
  CommitID:81c5c71c56b30105c85fc2478a1c65245af94b8d

132140-132142 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+


Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

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/27775/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2023-09-28 20:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28 20:00 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-29  0:26 dpdklab
2023-09-28 20:36 dpdklab
2023-09-28 20:03 dpdklab
2023-09-28 19:57 dpdklab
2023-09-28 18:38 dpdklab
2023-09-28 18:25 dpdklab
2023-09-28 18:23 dpdklab
2023-09-28 18:11 dpdklab
2023-09-28 18:03 dpdklab
2023-09-28 17:59 dpdklab
2023-09-28 17:59 dpdklab
2023-09-28 17:57 dpdklab
2023-09-28 17:54 dpdklab
2023-09-28 17:43 dpdklab
2023-09-28 17:31 dpdklab
2023-09-28 17:15 dpdklab
2023-09-28 17:14 dpdklab
2023-09-28 17:14 dpdklab
2023-09-28 17:14 dpdklab
2023-09-28 17:14 dpdklab
2023-09-28 17:12 dpdklab
2023-09-28 17:12 dpdklab
2023-09-28 17:09 dpdklab
2023-09-28 17:09 dpdklab
2023-09-28 17:08 dpdklab
2023-09-28 17:01 dpdklab
2023-09-28 17:01 dpdklab
2023-09-28 16:55 dpdklab
2023-09-28 16:47 dpdklab
2023-09-28 16:46 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=6515db5c.810a0220.270f8.fa0fSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=shunh@nvidia.com \
    --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).