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,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] 20db7deeb5131e46e859e212b334e8bef88ae701
Date: Sat, 16 Mar 2024 00:22:38 -0700 (PDT)	[thread overview]
Message-ID: <65f548be.050a0220.1f26f.0476SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-net

20db7deeb5131e46e859e212b334e8bef88ae701 --> testing pass

Test environment and result as below:

+--------------------------+---------------------------+------------------------------+----------------+
|       Environment        | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | dpdk_unit_test |
+==========================+===========================+==============================+================+
| Debian 12 (arm)          | PASS                      | PASS                         | PASS           |
+--------------------------+---------------------------+------------------------------+----------------+
| CentOS Stream 9 (ARM)    | SKIPPED                   | SKIPPED                      | PASS           |
+--------------------------+---------------------------+------------------------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED                   | SKIPPED                      | PASS           |
+--------------------------+---------------------------+------------------------------+----------------+
| Fedora 38 (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

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

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-03-16  7:22 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-16  7:22 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-19 19:57 dpdklab
2024-03-19 19:31 dpdklab
2024-03-16  8:24 dpdklab
2024-03-16  8:23 dpdklab
2024-03-16  7:58 dpdklab
2024-03-16  7:44 dpdklab
2024-03-16  7:42 dpdklab
2024-03-16  7:41 dpdklab
2024-03-16  7:40 dpdklab
2024-03-16  7:39 dpdklab
2024-03-16  7:37 dpdklab
2024-03-16  7:37 dpdklab
2024-03-16  7:37 dpdklab
2024-03-16  7:35 dpdklab
2024-03-16  7:32 dpdklab
2024-03-16  7:31 dpdklab
2024-03-16  7:31 dpdklab
2024-03-16  7:31 dpdklab
2024-03-16  7:30 dpdklab
2024-03-16  7:29 dpdklab
2024-03-16  7:28 dpdklab
2024-03-16  7:26 dpdklab
2024-03-16  7:25 dpdklab
2024-03-16  7:24 dpdklab
2024-03-16  7:20 dpdklab
2024-03-16  7:20 dpdklab
2024-03-16  7:20 dpdklab
2024-03-16  7:20 dpdklab
2024-03-16  7:16 dpdklab
2024-03-16  7:16 dpdklab
2024-03-16  7:16 dpdklab
2024-03-16  7:15 dpdklab
2024-03-16  7:15 dpdklab
2024-03-16  7:14 dpdklab
2024-03-16  7:14 dpdklab
2024-03-16  7:14 dpdklab
2024-03-16  7:14 dpdklab
2024-03-16  7:14 dpdklab
2024-03-16  7:14 dpdklab
2024-03-16  7:13 dpdklab
2024-03-16  7:13 dpdklab
2024-03-16  7:12 dpdklab
2024-03-16  7:12 dpdklab
2024-03-16  7:12 dpdklab
2024-03-16  7:12 dpdklab
2024-03-16  7:12 dpdklab
2024-03-16  7:11 dpdklab
2024-03-16  7:11 dpdklab
2024-03-16  7:10 dpdklab
2024-03-16  7:10 dpdklab
2024-03-16  7:10 dpdklab
2024-03-16  7:09 dpdklab
2024-03-16  7:09 dpdklab
2024-03-16  7:08 dpdklab
2024-03-16  7:08 dpdklab
2024-03-16  7:08 dpdklab
2024-03-16  7:07 dpdklab
2024-03-16  7:06 dpdklab
2024-03-16  6:49 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=65f548be.050a0220.1f26f.0476SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ferruh.yigit@amd.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).