From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] cfa8a4cb909e07cbb34941358f4d912c879dca34
Date: Sat, 13 Apr 2024 04:40:43 -0700 (PDT) [thread overview]
Message-ID: <661a6f3b.810a0220.529c0.6ba2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: 23.11-staging
cfa8a4cb909e07cbb34941358f4d912c879dca34 --> testing pass
Test environment and result as below:
+-----------------------------+--------------+----------------+------------------------------+---------------------------+
| Environment | lpm_autotest | dpdk_unit_test | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest |
+=============================+==============+================+==============================+===========================+
| Ubuntu 20.04 ARM SVE | PASS | SKIPPED | SKIPPED | SKIPPED |
+-----------------------------+--------------+----------------+------------------------------+---------------------------+
| 32-bit Ubuntu 20.04.4 (ARM) | SKIPPED | PASS | SKIPPED | SKIPPED |
+-----------------------------+--------------+----------------+------------------------------+---------------------------+
| CentOS Stream 9 (ARM) | SKIPPED | PASS | SKIPPED | SKIPPED |
+-----------------------------+--------------+----------------+------------------------------+---------------------------+
| Debian 11 (Buster) (ARM) | SKIPPED | PASS | SKIPPED | SKIPPED |
+-----------------------------+--------------+----------------+------------------------------+---------------------------+
| Fedora 38 (ARM) | SKIPPED | PASS | SKIPPED | SKIPPED |
+-----------------------------+--------------+----------------+------------------------------+---------------------------+
| Fedora 38 (ARM Clang) | SKIPPED | PASS | SKIPPED | SKIPPED |
+-----------------------------+--------------+----------------+------------------------------+---------------------------+
| Fedora 37 (ARM) | SKIPPED | PASS | SKIPPED | SKIPPED |
+-----------------------------+--------------+----------------+------------------------------+---------------------------+
| Debian 12 (arm) | SKIPPED | SKIPPED | PASS | PASS |
+-----------------------------+--------------+----------------+------------------------------+---------------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-167-generic
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
32-bit Ubuntu 20.04.4 (ARM)
Kernel: 5.4.0-155-generic aarch64
Compiler: gcc 9.4
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.4.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.2.1
Fedora 38 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 16.0.6
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28807/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-04-13 11:40 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-13 11:40 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-13 12:32 dpdklab
2024-04-13 12:28 dpdklab
2024-04-13 12:25 dpdklab
2024-04-13 12:23 dpdklab
2024-04-13 12:19 dpdklab
2024-04-13 12:09 dpdklab
2024-04-13 12:02 dpdklab
2024-04-13 11:48 dpdklab
2024-04-13 11:47 dpdklab
2024-04-13 11:39 dpdklab
2024-04-13 11:35 dpdklab
2024-04-13 11:23 dpdklab
2024-04-13 11:21 dpdklab
2024-04-13 11:17 dpdklab
2024-04-13 11:15 dpdklab
2024-04-13 11:08 dpdklab
2024-04-13 11:07 dpdklab
2024-04-13 11:04 dpdklab
2024-04-13 10:55 dpdklab
2024-04-13 10:52 dpdklab
2024-04-13 10:45 dpdklab
2024-04-13 10:43 dpdklab
2024-04-13 10:26 dpdklab
2024-04-13 10:24 dpdklab
2024-04-13 10:22 dpdklab
2024-04-13 10:21 dpdklab
2024-04-13 10:18 dpdklab
2024-04-13 10:16 dpdklab
2024-04-13 10:15 dpdklab
2024-04-13 10:15 dpdklab
2024-04-13 10:15 dpdklab
2024-04-13 10:13 dpdklab
2024-04-13 10:09 dpdklab
2024-04-13 10:08 dpdklab
2024-04-13 10:04 dpdklab
2024-04-13 10:03 dpdklab
2024-04-13 10:02 dpdklab
2024-04-13 10:00 dpdklab
2024-04-13 9:59 dpdklab
2024-04-13 9:58 dpdklab
2024-04-13 9:58 dpdklab
2024-04-13 9:57 dpdklab
2024-04-13 9:56 dpdklab
2024-04-13 9:56 dpdklab
2024-04-13 9:55 dpdklab
2024-04-13 9:54 dpdklab
2024-04-13 9:54 dpdklab
2024-04-13 9:53 dpdklab
2024-04-13 9:51 dpdklab
2024-04-13 9:51 dpdklab
2024-04-13 9:50 dpdklab
2024-04-13 9:50 dpdklab
2024-04-13 9:49 dpdklab
2024-04-13 9:49 dpdklab
2024-04-13 9:49 dpdklab
2024-04-13 9:48 dpdklab
2024-04-13 9:48 dpdklab
2024-04-13 9:47 dpdklab
2024-04-13 9:47 dpdklab
2024-04-13 9:46 dpdklab
2024-04-13 9:45 dpdklab
2024-04-13 9:45 dpdklab
2024-04-13 9:43 dpdklab
2024-04-13 9:43 dpdklab
2024-04-13 9:41 dpdklab
2024-04-13 9:39 dpdklab
2024-04-13 9:38 dpdklab
2024-04-13 9:38 dpdklab
2024-04-13 9:38 dpdklab
2024-04-13 9:37 dpdklab
2024-04-13 9:37 dpdklab
2024-04-13 9:36 dpdklab
2024-04-13 9:28 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=661a6f3b.810a0220.529c0.6ba2SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).