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| pw128530 [PATCH] [v3] net/cnxk: support port ID flow actio
Date: Tue, 13 Jun 2023 00:45:25 -0700 (PDT)	[thread overview]
Message-ID: <64881e95.170a0220.864a0.bfbfSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Satheesh Paul Antonysamy <psatheesh@marvell.com>
Date: Tuesday, June 13 2023 04:56:52 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:050de60d8a5cef8b7c10b4471905ca8bf69d670e

128530 --> testing pass

Test environment and result as below:

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


Debian 11
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-06-13  7:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13  7:45 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-13 22:07 dpdklab
2023-06-13 21:57 dpdklab
2023-06-13 21:52 dpdklab
2023-06-13 21:48 dpdklab
2023-06-13 21:33 dpdklab
2023-06-13 21:32 dpdklab
2023-06-13 13:14 dpdklab
2023-06-13 13:13 dpdklab
2023-06-13 11:15 dpdklab
2023-06-13 10:53 dpdklab
2023-06-13  8:30 dpdklab
2023-06-13  8:25 dpdklab
2023-06-13  8:15 dpdklab
2023-06-13  8:07 dpdklab
2023-06-13  8:04 dpdklab
2023-06-13  8:04 dpdklab
2023-06-13  8:00 dpdklab
2023-06-13  7:59 dpdklab
2023-06-13  7:57 dpdklab
2023-06-13  7:51 dpdklab
2023-06-13  7:48 dpdklab
2023-06-13  7:45 dpdklab
2023-06-13  7:10 dpdklab
2023-06-13  7:05 dpdklab
2023-06-13  7:05 dpdklab
2023-06-13  7:03 dpdklab
2023-06-13  7:03 dpdklab
2023-06-13  6: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=64881e95.170a0220.864a0.bfbfSMTPIN_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).