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] 1ff69fa228b1313bb0c430a5cd0d4d5d26fc93e3
Date: Mon, 04 Mar 2024 13:13:16 -0800 (PST)	[thread overview]
Message-ID: <65e6396c.050a0220.3b082.4589SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-crypto

1ff69fa228b1313bb0c430a5cd0d4d5d26fc93e3 --> testing pass

Test environment and result as below:

+-----------------------+------------------------------+---------------------------+----------------+
|      Environment      | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest | dpdk_unit_test |
+=======================+==============================+===========================+================+
| Debian 12 (arm)       | PASS                         | PASS                      | PASS           |
+-----------------------+------------------------------+---------------------------+----------------+
| CentOS Stream 9 (ARM) | SKIPPED                      | SKIPPED                   | PASS           |
+-----------------------+------------------------------+---------------------------+----------------+


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

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-03-04 21:13 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 21:13 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-08 11:46 dpdklab
2024-03-08 11:25 dpdklab
2024-03-08 10:37 dpdklab
2024-03-04 22:26 dpdklab
2024-03-04 22:08 dpdklab
2024-03-04 21:45 dpdklab
2024-03-04 21:28 dpdklab
2024-03-04 21:26 dpdklab
2024-03-04 21:26 dpdklab
2024-03-04 21:25 dpdklab
2024-03-04 21:25 dpdklab
2024-03-04 21:23 dpdklab
2024-03-04 21:23 dpdklab
2024-03-04 21:22 dpdklab
2024-03-04 21:22 dpdklab
2024-03-04 21:21 dpdklab
2024-03-04 21:21 dpdklab
2024-03-04 21:20 dpdklab
2024-03-04 21:19 dpdklab
2024-03-04 21:18 dpdklab
2024-03-04 21:17 dpdklab
2024-03-04 21:17 dpdklab
2024-03-04 21:17 dpdklab
2024-03-04 21:15 dpdklab
2024-03-04 21:15 dpdklab
2024-03-04 21:14 dpdklab
2024-03-04 21:13 dpdklab
2024-03-04 21:12 dpdklab
2024-03-04 21:12 dpdklab
2024-03-04 21:12 dpdklab
2024-03-04 21:11 dpdklab
2024-03-04 21:10 dpdklab
2024-03-04 21:10 dpdklab
2024-03-04 21:09 dpdklab
2024-03-04 21:09 dpdklab
2024-03-04 21:08 dpdklab
2024-03-04 21:08 dpdklab
2024-03-04 21:08 dpdklab
2024-03-04 21:08 dpdklab
2024-03-04 21:07 dpdklab
2024-03-04 21:07 dpdklab
2024-03-04 21:07 dpdklab
2024-03-04 21:07 dpdklab
2024-03-04 21:07 dpdklab
2024-03-04 21:07 dpdklab
2024-03-04 21:06 dpdklab
2024-03-04 21:06 dpdklab
2024-03-04 21:06 dpdklab
2024-03-04 21:06 dpdklab
2024-03-04 21:05 dpdklab
2024-03-04 21:05 dpdklab
2024-03-04 21:04 dpdklab
2024-03-04 21:04 dpdklab
2024-03-04 21:04 dpdklab
2024-03-04 21:04 dpdklab
2024-03-04 21:04 dpdklab
2024-03-04 21:03 dpdklab
2024-03-04 21:03 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=65e6396c.050a0220.3b082.4589SMTPIN_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).