automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125896 [PATCH] common/cnxk: update ROC erratas
Date: Tue, 11 Apr 2023 12:38:16 +0000 (UTC)	[thread overview]
Message-ID: <20230411123816.5685E60092@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

Test-Label: iol-aarch64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/125896

_Testing PASS_

Submitter: Ashwin Sekhar T K <asekhar@marvell.com>
Date: Tuesday, April 11 2023 07:18:31 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:65487b12db83c9ef37526a983c43191cd44dae99

125896 --> testing pass

Test environment and result as below:

+----------------------+------------------------------+---------------------------+--------------+
|     Environment      | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest | lpm_autotest |
+======================+==============================+===========================+==============+
| Debian 11            | PASS                         | PASS                      | SKIPPED      |
+----------------------+------------------------------+---------------------------+--------------+
| Ubuntu 20.04 ARM SVE | 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)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-04-11 12:38 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 12:38 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-12 23:42 dpdklab
2023-04-12 23:26 dpdklab
2023-04-12 23:21 dpdklab
2023-04-12 23:17 dpdklab
2023-04-12 23:02 dpdklab
2023-04-12 22:57 dpdklab
2023-04-11 15:54 dpdklab
2023-04-11 15:53 dpdklab
2023-04-11 15:39 dpdklab
2023-04-11 15:18 dpdklab
2023-04-11 15:18 dpdklab
2023-04-11 14:18 dpdklab
2023-04-11 13:55 dpdklab
2023-04-11 13:48 dpdklab
2023-04-11 13:46 dpdklab
2023-04-11 13:46 dpdklab
2023-04-11 13:45 dpdklab
2023-04-11 13:43 dpdklab
2023-04-11 13:42 dpdklab
2023-04-11 13:34 dpdklab
2023-04-11 13:34 dpdklab
2023-04-11 13:27 dpdklab
2023-04-11 13:26 dpdklab
2023-04-11 13:17 dpdklab
2023-04-11 13:15 dpdklab
2023-04-11 13:13 dpdklab
2023-04-11 13:08 dpdklab
2023-04-11 13:07 dpdklab
2023-04-11 13:07 dpdklab
2023-04-11 12:57 dpdklab
2023-04-11 12:56 dpdklab
2023-04-11 12:55 dpdklab
2023-04-11 12:55 dpdklab
2023-04-11 12:54 dpdklab
2023-04-11 12:54 dpdklab
2023-04-11 12:53 dpdklab
2023-04-11 12:52 dpdklab
2023-04-11 12:52 dpdklab
2023-04-11 12:52 dpdklab
2023-04-11 12:50 dpdklab
2023-04-11 12:43 dpdklab
2023-04-11 12:42 dpdklab
2023-04-11 12:41 dpdklab
2023-04-11 12:39 dpdklab
2023-04-11 12:39 dpdklab
2023-04-11 12:39 dpdklab
2023-04-11 12:37 dpdklab
2023-04-11 12:33 dpdklab
2023-04-11 12:31 dpdklab
2023-04-11 12:26 dpdklab
2023-04-11 12:26 dpdklab
2023-04-11 12:24 dpdklab
2023-04-11 12:24 dpdklab
2023-04-11 12:22 dpdklab
2023-04-11 12:19 dpdklab
2023-04-11 12:17 dpdklab
     [not found] <20230411071831.1124587-1-asekhar@marvell.com>
2023-04-11  7:07 ` qemudev
2023-04-11  7:11 ` qemudev
2023-04-11  7:19 ` checkpatch
2023-04-11  8:18 ` 0-day Robot

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=20230411123816.5685E60092@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).