automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133651-133660 [PATCH] [10/10] net/mlx5/hws: dynamic re-p
Date: Tue, 31 Oct 2023 06:14:38 -0700 (PDT)	[thread overview]
Message-ID: <6540fdbe.170a0220.b6aee.3ab4SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133660

_Testing PASS_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Tuesday, October 31 2023 12:25:12 
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: master
  CommitID:441197cc1ab413c379a88abbcf8e98b195c8eb76

133651-133660 --> testing pass

Test environment and result as below:

+----------------------+------------------------------+--------------+
|     Environment      | cryptodev_sw_snow3g_autotest | lpm_autotest |
+======================+==============================+==============+
| Debian 11 (arm)      | PASS                         | SKIPPED      |
+----------------------+------------------------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED                      | PASS         |
+----------------------+------------------------------+--------------+


Debian 11 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.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/28157/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-31 13:14 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 13:14 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-31 16:07 dpdklab
2023-10-31 15:18 dpdklab
2023-10-31 15:18 dpdklab
2023-10-31 14:35 dpdklab
2023-10-31 14:31 dpdklab
2023-10-31 14:13 dpdklab
2023-10-31 13:51 dpdklab
2023-10-31 13:44 dpdklab
2023-10-31 13:40 dpdklab
2023-10-31 13:40 dpdklab
2023-10-31 13:36 dpdklab
2023-10-31 13:35 dpdklab
2023-10-31 13:35 dpdklab
2023-10-31 13:34 dpdklab
2023-10-31 13:32 dpdklab
2023-10-31 13:32 dpdklab
2023-10-31 13:32 dpdklab
2023-10-31 13:30 dpdklab
2023-10-31 13:28 dpdklab
2023-10-31 13:28 dpdklab
2023-10-31 13:26 dpdklab
2023-10-31 13:25 dpdklab
2023-10-31 13:24 dpdklab
2023-10-31 13:23 dpdklab
2023-10-31 13:22 dpdklab
2023-10-31 13:22 dpdklab
2023-10-31 13:21 dpdklab
2023-10-31 13:20 dpdklab
2023-10-31 13:20 dpdklab
2023-10-31 13:19 dpdklab
2023-10-31 13:19 dpdklab
2023-10-31 13:19 dpdklab
2023-10-31 13:19 dpdklab
2023-10-31 13:19 dpdklab
2023-10-31 13:19 dpdklab
2023-10-31 13:18 dpdklab
2023-10-31 13:18 dpdklab
2023-10-31 13:18 dpdklab
2023-10-31 13:16 dpdklab
2023-10-31 13:16 dpdklab
2023-10-31 13:15 dpdklab
2023-10-31 13:15 dpdklab
2023-10-31 13:14 dpdklab
2023-10-31 13:14 dpdklab
2023-10-31 13:13 dpdklab
2023-10-31 13:13 dpdklab
2023-10-31 13:12 dpdklab
2023-10-31 13:12 dpdklab
2023-10-31 13:12 dpdklab
2023-10-31 13:11 dpdklab
2023-10-31 13:11 dpdklab
2023-10-31 13:11 dpdklab
2023-10-31 13:11 dpdklab
2023-10-31 13:10 dpdklab
2023-10-31 13:10 dpdklab
2023-10-31 13:09 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=6540fdbe.170a0220.b6aee.3ab4SMTPIN_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).