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] 623dc9364dc6a818799941cc26dc8f70feb2bb24
Date: Fri, 07 Jul 2023 18:26:58 -0700 (PDT)	[thread overview]
Message-ID: <64a8bb62.0c0a0220.67eb7.776aSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk

623dc9364dc6a818799941cc26dc8f70feb2bb24 --> testing pass

Test environment and result as below:

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


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/tarballs/25415/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-07-08  1:27 UTC|newest]

Thread overview: 145+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-08  1:26 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-14 12:59 dpdklab
2023-07-14 12:53 dpdklab
2023-07-14 12:48 dpdklab
2023-07-14  8:15 dpdklab
2023-07-14  8:10 dpdklab
2023-07-14  8:05 dpdklab
2023-07-14  2:21 dpdklab
2023-07-14  1:28 dpdklab
2023-07-14  1:23 dpdklab
2023-07-14  0:51 dpdklab
2023-07-13 23:54 dpdklab
2023-07-13 23:50 dpdklab
2023-07-13 17:00 dpdklab
2023-07-13 16:56 dpdklab
2023-07-13 15:34 dpdklab
2023-07-13 15:34 dpdklab
2023-07-13 13:55 dpdklab
2023-07-13 13:44 dpdklab
2023-07-13 13:44 dpdklab
2023-07-13 13:44 dpdklab
2023-07-13  5:50 dpdklab
2023-07-13  5:32 dpdklab
2023-07-13  4:49 dpdklab
2023-07-13  4:32 dpdklab
2023-07-13  3:40 dpdklab
2023-07-13  3:28 dpdklab
2023-07-13  3:00 dpdklab
2023-07-13  2:54 dpdklab
2023-07-12  4:54 dpdklab
2023-07-12  3:52 dpdklab
2023-07-11 13:57 dpdklab
2023-07-11 13:57 dpdklab
2023-07-11 13:54 dpdklab
2023-07-11 13:54 dpdklab
2023-07-11 13:54 dpdklab
2023-07-11 13:53 dpdklab
2023-07-11 13:53 dpdklab
2023-07-11 13:53 dpdklab
2023-07-11 13:52 dpdklab
2023-07-11 13:52 dpdklab
2023-07-11 13:51 dpdklab
2023-07-11 13:51 dpdklab
2023-07-11 13:50 dpdklab
2023-07-11 13:47 dpdklab
2023-07-11  6:43 dpdklab
2023-07-11  6:17 dpdklab
2023-07-11  2:13 dpdklab
2023-07-11  1:29 dpdklab
2023-07-11  1:17 dpdklab
2023-07-11  1:16 dpdklab
2023-07-10 21:01 dpdklab
2023-07-10 21:00 dpdklab
2023-07-10 21:00 dpdklab
2023-07-10 20:58 dpdklab
2023-07-10 20:56 dpdklab
2023-07-10  1:56 dpdklab
2023-07-10  1:55 dpdklab
2023-07-10  1:54 dpdklab
2023-07-10  1:49 dpdklab
2023-07-10  1:43 dpdklab
2023-07-10  1:40 dpdklab
2023-07-10  1:38 dpdklab
2023-07-10  1:36 dpdklab
2023-07-10  1:31 dpdklab
2023-07-10  1:19 dpdklab
2023-07-10  1:13 dpdklab
2023-07-10  1:13 dpdklab
2023-07-10  1:06 dpdklab
2023-07-10  1:05 dpdklab
2023-07-10  1:04 dpdklab
2023-07-10  1:02 dpdklab
2023-07-10  0:59 dpdklab
2023-07-09 17:47 dpdklab
2023-07-09 17:28 dpdklab
2023-07-09 13:43 dpdklab
2023-07-09 13:22 dpdklab
2023-07-09  1:55 dpdklab
2023-07-09  1:52 dpdklab
2023-07-09  1:51 dpdklab
2023-07-09  1:50 dpdklab
2023-07-09  1:34 dpdklab
2023-07-09  1:28 dpdklab
2023-07-09  1:26 dpdklab
2023-07-09  1:21 dpdklab
2023-07-09  1:17 dpdklab
2023-07-09  1:15 dpdklab
2023-07-09  1:09 dpdklab
2023-07-09  1:07 dpdklab
2023-07-09  1:06 dpdklab
2023-07-09  1:05 dpdklab
2023-07-09  1:05 dpdklab
2023-07-09  1:04 dpdklab
2023-07-09  1:04 dpdklab
2023-07-08  1:36 dpdklab
2023-07-08  1:35 dpdklab
2023-07-08  1:23 dpdklab
2023-07-08  1:22 dpdklab
2023-07-08  1:20 dpdklab
2023-07-08  1:19 dpdklab
2023-07-08  1:15 dpdklab
2023-07-08  1:09 dpdklab
2023-07-08  1:08 dpdklab
2023-07-08  1:07 dpdklab
2023-07-08  1:07 dpdklab
2023-07-08  1:07 dpdklab
2023-07-08  1:07 dpdklab
2023-07-08  1:06 dpdklab
2023-07-08  1:06 dpdklab
2023-07-08  1:06 dpdklab
2023-07-07 17:24 dpdklab
2023-07-07 17:19 dpdklab
2023-07-07 17:17 dpdklab
2023-07-07 17:13 dpdklab
2023-07-07 17:11 dpdklab
2023-07-07 17:11 dpdklab
2023-07-07 17:09 dpdklab
2023-07-07 17:09 dpdklab
2023-07-07 17:08 dpdklab
2023-07-07 17:08 dpdklab
2023-07-07 17:06 dpdklab
2023-07-07 17:01 dpdklab
2023-07-07 17:01 dpdklab
2023-07-07 17:01 dpdklab
2023-07-07 17:01 dpdklab
2023-07-07 17:00 dpdklab
2023-07-07 17:00 dpdklab
2023-07-07 17:00 dpdklab
2023-07-07 17:00 dpdklab
2023-07-07 16:59 dpdklab
2023-07-07 16:59 dpdklab
2023-07-07 16:59 dpdklab
2023-07-07 16:32 dpdklab
2023-07-07 16:28 dpdklab
2023-07-07 16:18 dpdklab
2023-07-07 16:16 dpdklab
2023-07-07 16:16 dpdklab
2023-07-07 16:16 dpdklab
2023-07-07 16:16 dpdklab
2023-07-07 16:16 dpdklab
2023-07-07 16:16 dpdklab
2023-07-07 16:15 dpdklab
2023-07-07 16:15 dpdklab
2023-07-07 16:15 dpdklab
2023-07-07 16:14 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=64a8bb62.0c0a0220.67eb7.776aSMTPIN_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).