automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Rongwei Liu <rongweil@nvidia.com>, dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw128505 [PATCH] [v1] net/mlx5: adapt parse graph header l
Date: Mon, 12 Jun 2023 06:30:52 -0700 (PDT)	[thread overview]
Message-ID: <64871e0c.810a0220.81256.e327SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Rongwei Liu <rongweil@nvidia.com>
Date: Monday, June 12 2023 08:04:08 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:abb4cc0efc1b0f7779bbe3e24bcb362146351c6e

128505 --> testing pass

Test environment and result as below:

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


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

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)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-06-12 13:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 13:30 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-12 15:17 dpdklab
2023-06-12 15:10 dpdklab
2023-06-12 15:00 dpdklab
2023-06-12 14:55 dpdklab
2023-06-12 14:51 dpdklab
2023-06-12 14:22 dpdklab
2023-06-12 14:11 dpdklab
2023-06-12 14:06 dpdklab
2023-06-12 14:05 dpdklab
2023-06-12 13:43 dpdklab
2023-06-12 13:43 dpdklab
2023-06-12 13:20 dpdklab
2023-06-12 13:17 dpdklab
2023-06-12 13:15 dpdklab
2023-06-12 13:13 dpdklab
2023-06-12 13:13 dpdklab
2023-06-12 13:12 dpdklab
2023-06-12 13:12 dpdklab
2023-06-12 13:08 dpdklab
2023-06-12 13:07 dpdklab
2023-06-12 13:03 dpdklab
2023-06-12 12:52 dpdklab
2023-06-12 12:48 dpdklab
2023-06-12 12:46 dpdklab
2023-06-12 12:46 dpdklab
2023-06-12 12:45 dpdklab
2023-06-12 12: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=64871e0c.810a0220.81256.e327SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=rongweil@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).