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| [GIT MASTER] baaa446dd47ec05a93bb1843fc49791c8fa21697
Date: Tue, 21 Nov 2023 18:12:34 -0800 (PST)	[thread overview]
Message-ID: <655d6392.250a0220.4afa2.f60eSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk

baaa446dd47ec05a93bb1843fc49791c8fa21697 --> testing pass

Test environment and result as below:

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


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

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

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-22  2:12 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22  2:12 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-22  3:21 dpdklab
2023-11-22  3:05 dpdklab
2023-11-22  3:01 dpdklab
2023-11-22  3:00 dpdklab
2023-11-22  2:37 dpdklab
2023-11-22  2:32 dpdklab
2023-11-22  2:31 dpdklab
2023-11-22  2:30 dpdklab
2023-11-22  2:30 dpdklab
2023-11-22  2:29 dpdklab
2023-11-22  2:27 dpdklab
2023-11-22  2:27 dpdklab
2023-11-22  2:27 dpdklab
2023-11-22  2:24 dpdklab
2023-11-22  2:23 dpdklab
2023-11-22  2:23 dpdklab
2023-11-22  2:21 dpdklab
2023-11-22  2:20 dpdklab
2023-11-22  2:20 dpdklab
2023-11-22  2:19 dpdklab
2023-11-22  2:18 dpdklab
2023-11-22  2:17 dpdklab
2023-11-22  2:17 dpdklab
2023-11-22  2:16 dpdklab
2023-11-22  2:15 dpdklab
2023-11-22  2:13 dpdklab
2023-11-22  2:13 dpdklab
2023-11-22  2:11 dpdklab
2023-11-22  2:11 dpdklab
2023-11-22  2:09 dpdklab
2023-11-22  2:09 dpdklab
2023-11-22  2:09 dpdklab
2023-11-22  2:09 dpdklab
2023-11-22  2:07 dpdklab
2023-11-22  2:06 dpdklab
2023-11-22  2:06 dpdklab
2023-11-22  2:06 dpdklab
2023-11-22  2:06 dpdklab
2023-11-22  2:06 dpdklab
2023-11-22  2:05 dpdklab
2023-11-22  2:05 dpdklab
2023-11-22  2:05 dpdklab
2023-11-22  2:05 dpdklab
2023-11-22  2:04 dpdklab
2023-11-22  2:04 dpdklab
2023-11-22  2:04 dpdklab
2023-11-22  2:03 dpdklab
2023-11-22  2:03 dpdklab
2023-11-22  2:03 dpdklab
2023-11-22  2:03 dpdklab
2023-11-22  2:02 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=655d6392.250a0220.4afa2.f60eSMTPIN_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).