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| pw129186 [PATCH] doc: update mlxreg command arguments for
Date: Thu, 06 Jul 2023 00:20:16 -0700 (PDT)	[thread overview]
Message-ID: <64a66b30.0c0a0220.e81f2.21dcSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-aarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/129186

_Testing PASS_

Submitter: Ali Alnubani <alialnu@nvidia.com>
Date: Monday, July 03 2023 07:48:20 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a64a4564705d18d20d20cfa16c79e795b7bf0f1e

129186 --> testing pass

Test environment and result as below:

+-----------------------------+---------------------------+------------------------------+--------------+----------------+
|         Environment         | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | lpm_autotest | dpdk_unit_test |
+=============================+===========================+==============================+==============+================+
| Debian 11                   | PASS                      | PASS                         | SKIPPED      | SKIPPED        |
+-----------------------------+---------------------------+------------------------------+--------------+----------------+
| Ubuntu 20.04 ARM SVE        | SKIPPED                   | SKIPPED                      | PASS         | SKIPPED        |
+-----------------------------+---------------------------+------------------------------+--------------+----------------+
| (32-bit) ARM Ubuntu 20.04.4 | SKIPPED                   | SKIPPED                      | SKIPPED      | PASS           |
+-----------------------------+---------------------------+------------------------------+--------------+----------------+


Debian 11
	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)

(32-bit) ARM Ubuntu 20.04.4
	Kernel: 5.4.0-148-generic aarch64
	Compiler: gcc 9.4

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26919/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-07-06  7:20 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06  7:20 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-15  2:28 dpdklab
2023-07-15  2:28 dpdklab
2023-07-12 17:30 dpdklab
2023-07-12  2:43 dpdklab
2023-07-12  2:40 dpdklab
2023-07-12  2:07 dpdklab
2023-07-12  0:27 dpdklab
2023-07-11 23:21 dpdklab
2023-07-11 21:43 dpdklab
2023-07-11 21:29 dpdklab
2023-07-10 21:48 dpdklab
2023-07-08  3:08 dpdklab
2023-07-08  2:26 dpdklab
2023-07-06 19:31 dpdklab
2023-07-06  9:33 dpdklab
2023-07-06  7:31 dpdklab
2023-07-06  4:05 dpdklab
2023-07-06  3:57 dpdklab
2023-07-06  3:36 dpdklab
2023-07-06  3:35 dpdklab
2023-07-06  3:33 dpdklab
2023-07-06  3:31 dpdklab
2023-07-06  3:26 dpdklab
2023-07-06  3:23 dpdklab
2023-07-06  3:22 dpdklab
2023-07-06  3:21 dpdklab
2023-07-06  3:21 dpdklab
2023-07-06  3:03 dpdklab
2023-07-06  3:01 dpdklab
2023-07-06  2:42 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=64a66b30.0c0a0220.e81f2.21dcSMTPIN_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).