From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 90a91f8761af9f99243e1ca35082fcf05ff7a9b2
Date: Fri, 15 Mar 2024 09:20:46 -0700 (PDT) [thread overview]
Message-ID: <65f4755e.050a0220.a471f.bb20SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
90a91f8761af9f99243e1ca35082fcf05ff7a9b2 --> testing pass
Test environment and result as below:
+--------------------------+--------------+----------------+------------------------------+
| Environment | lpm_autotest | dpdk_unit_test | cryptodev_sw_snow3g_autotest |
+==========================+==============+================+==============================+
| Ubuntu 20.04 ARM SVE | PASS | SKIPPED | SKIPPED |
+--------------------------+--------------+----------------+------------------------------+
| CentOS Stream 9 (ARM) | SKIPPED | PASS | SKIPPED |
+--------------------------+--------------+----------------+------------------------------+
| Debian 11 (Buster) (ARM) | SKIPPED | PASS | SKIPPED |
+--------------------------+--------------+----------------+------------------------------+
| Fedora 37 (ARM) | SKIPPED | PASS | SKIPPED |
+--------------------------+--------------+----------------+------------------------------+
| Debian 12 (arm) | SKIPPED | PASS | PASS |
+--------------------------+--------------+----------------+------------------------------+
| Fedora 38 (ARM) | SKIPPED | PASS | SKIPPED |
+--------------------------+--------------+----------------+------------------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
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 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
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/28506/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-03-15 16:20 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 16:20 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-19 10:00 dpdklab
2024-03-19 9:24 dpdklab
2024-03-15 17:13 dpdklab
2024-03-15 17:09 dpdklab
2024-03-15 16:49 dpdklab
2024-03-15 16:23 dpdklab
2024-03-15 16:21 dpdklab
2024-03-15 16:20 dpdklab
2024-03-15 16:16 dpdklab
2024-03-15 16:16 dpdklab
2024-03-15 16:15 dpdklab
2024-03-15 16:15 dpdklab
2024-03-15 16:11 dpdklab
2024-03-15 16:11 dpdklab
2024-03-15 16:11 dpdklab
2024-03-15 16:10 dpdklab
2024-03-15 16:10 dpdklab
2024-03-15 16:10 dpdklab
2024-03-15 16:09 dpdklab
2024-03-15 16:08 dpdklab
2024-03-15 16:08 dpdklab
2024-03-15 16:07 dpdklab
2024-03-15 16:07 dpdklab
2024-03-15 16:07 dpdklab
2024-03-15 16:07 dpdklab
2024-03-15 16:06 dpdklab
2024-03-15 16:06 dpdklab
2024-03-15 16:06 dpdklab
2024-03-15 16:06 dpdklab
2024-03-15 16:05 dpdklab
2024-03-15 16:05 dpdklab
2024-03-15 16:05 dpdklab
2024-03-15 16:05 dpdklab
2024-03-15 16:04 dpdklab
2024-03-15 16:04 dpdklab
2024-03-15 16:04 dpdklab
2024-03-15 16:04 dpdklab
2024-03-15 16:04 dpdklab
2024-03-15 16:04 dpdklab
2024-03-15 16:04 dpdklab
2024-03-15 16:03 dpdklab
2024-03-15 16:03 dpdklab
2024-03-15 16:03 dpdklab
2024-03-15 16:03 dpdklab
2024-03-15 16:02 dpdklab
2024-03-15 16:02 dpdklab
2024-03-15 16:02 dpdklab
2024-03-15 16:01 dpdklab
2024-03-15 16:01 dpdklab
2024-03-15 16:01 dpdklab
2024-03-15 16:01 dpdklab
2024-03-15 16:01 dpdklab
2024-03-15 16:00 dpdklab
2024-03-15 16:00 dpdklab
2024-03-15 16:00 dpdklab
2024-03-15 16:00 dpdklab
2024-03-15 15:59 dpdklab
2024-03-15 15:59 dpdklab
2024-03-15 15:59 dpdklab
2024-03-15 15:59 dpdklab
2024-03-15 15:58 dpdklab
2024-03-15 15:58 dpdklab
2024-03-15 15:58 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=65f4755e.050a0220.a471f.bb20SMTPIN_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).