automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Tejasree Kondoj <ktejasree@marvell.com>, dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw128790-128797 [PATCH] [8/8] crypto/cnxk: fix order of EC
Date: Mon, 19 Jun 2023 06:57:09 -0700 (PDT)	[thread overview]
Message-ID: <64905eb5.170a0220.6d223.8424SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Tejasree Kondoj <ktejasree@marvell.com>
Date: Monday, June 19 2023 12:49:41 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7556a1a355fb377279508735f7afc1faf1d00158

128790-128797 --> testing pass

Test environment and result as below:

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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-06-19 13:57 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-19 13:57 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-21  1:34 dpdklab
2023-06-21  1:29 dpdklab
2023-06-20 20:20 dpdklab
2023-06-20 20:20 dpdklab
2023-06-19 16:14 dpdklab
2023-06-19 14:48 dpdklab
2023-06-19 14:28 dpdklab
2023-06-19 14:06 dpdklab
2023-06-19 14:01 dpdklab
2023-06-19 14:00 dpdklab
2023-06-19 13:59 dpdklab
2023-06-19 13:56 dpdklab
2023-06-19 13:49 dpdklab
2023-06-19 13:49 dpdklab
2023-06-19 13:48 dpdklab
2023-06-19 13:47 dpdklab
2023-06-19 13:47 dpdklab
2023-06-19 13:46 dpdklab
2023-06-19 13:43 dpdklab
2023-06-19 13:40 dpdklab
2023-06-19 13:36 dpdklab
2023-06-19 13:36 dpdklab
2023-06-19 13:33 dpdklab
2023-06-19 13:33 dpdklab
2023-06-19 13:33 dpdklab
2023-06-19 13:33 dpdklab
2023-06-19 13:32 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=64905eb5.170a0220.6d223.8424SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ktejasree@marvell.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).