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, Akhil Goyal <gakhil@marvell.com>
Subject: |SUCCESS| [GIT MASTER] 5ac50824383c2683c0dfdf24c6dc493f1fa54852
Date: Fri, 01 Mar 2024 20:02:53 -0800 (PST)	[thread overview]
Message-ID: <65e2a4ed.810a0220.acce1.2749SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-crypto

5ac50824383c2683c0dfdf24c6dc493f1fa54852 --> testing pass

Test environment and result as below:

+----------------------+--------------+---------------------------+------------------------------+
|     Environment      | lpm_autotest | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest |
+======================+==============+===========================+==============================+
| Ubuntu 20.04 ARM SVE | PASS         | SKIPPED                   | SKIPPED                      |
+----------------------+--------------+---------------------------+------------------------------+
| Debian 12 (arm)      | SKIPPED      | PASS                      | PASS                         |
+----------------------+--------------+---------------------------+------------------------------+


Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-80-generic
	Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)

Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 11

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28275/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-03-02  4:02 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-02  4:02 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-06 11:30 dpdklab
2024-03-06 10:55 dpdklab
2024-03-06 10:31 dpdklab
2024-03-03  4:16 dpdklab
2024-03-02  6:03 dpdklab
2024-03-02  5:22 dpdklab
2024-03-02  4:44 dpdklab
2024-03-02  4:24 dpdklab
2024-03-02  4:18 dpdklab
2024-03-02  4:17 dpdklab
2024-03-02  4:16 dpdklab
2024-03-02  4:11 dpdklab
2024-03-02  4:10 dpdklab
2024-03-02  4:00 dpdklab
2024-03-02  3:13 dpdklab
2024-03-02  3:08 dpdklab
2024-03-02  3:07 dpdklab
2024-03-02  3:01 dpdklab
2024-03-02  3:01 dpdklab
2024-03-02  3:00 dpdklab
2024-03-02  3:00 dpdklab
2024-03-02  2:59 dpdklab
2024-03-02  2:59 dpdklab
2024-03-02  2:59 dpdklab
2024-03-02  2:59 dpdklab
2024-03-02  2:59 dpdklab
2024-03-02  2:58 dpdklab
2024-03-02  2:58 dpdklab
2024-03-02  2:58 dpdklab
2024-03-02  2:57 dpdklab
2024-03-02  2:57 dpdklab
2024-03-02  2:57 dpdklab
2024-03-02  2:57 dpdklab
2024-03-02  2:57 dpdklab
2024-03-02  2:56 dpdklab
2024-03-02  2:56 dpdklab
2024-03-02  2:56 dpdklab
2024-03-02  2:56 dpdklab
2024-03-02  2:56 dpdklab
2024-03-02  2:56 dpdklab
2024-03-02  2:56 dpdklab
2024-03-02  2:55 dpdklab
2024-03-02  2:55 dpdklab
2024-03-02  2:55 dpdklab
2024-03-02  2:54 dpdklab
2024-03-02  2:54 dpdklab
2024-03-02  2:54 dpdklab
2024-03-02  2:53 dpdklab
2024-03-02  1:19 dpdklab
2024-03-02  1:18 dpdklab
2024-03-02  1:16 dpdklab
2024-03-02  1:12 dpdklab
2024-03-02  0:01 dpdklab
2024-03-01 23:57 dpdklab
2024-03-01 23:56 dpdklab
2024-03-01 23:56 dpdklab
2024-03-01 23:55 dpdklab
2024-03-01 23:53 dpdklab
2024-03-01 23:33 dpdklab
2024-03-01 23:25 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=65e2a4ed.810a0220.acce1.2749SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=gakhil@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).