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] 6db5f91b5e628671c341b833f21ea35e65e9699d
Date: Thu, 11 Apr 2024 23:50:34 -0700 (PDT) [thread overview]
Message-ID: <6618d9ba.0d0a0220.29aae.b089SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
6db5f91b5e628671c341b833f21ea35e65e9699d --> testing pass
Test environment and result as below:
+--------------------------+---------------------------+------------------------------+--------------+----------------+
| Environment | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | lpm_autotest | dpdk_unit_test |
+==========================+===========================+==============================+==============+================+
| Debian 12 (arm) | PASS | PASS | SKIPPED | SKIPPED |
+--------------------------+---------------------------+------------------------------+--------------+----------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | SKIPPED | PASS | SKIPPED |
+--------------------------+---------------------------+------------------------------+--------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED | SKIPPED | SKIPPED | PASS |
+--------------------------+---------------------------+------------------------------+--------------+----------------+
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-167-generic
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
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/28790/
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-12 6:50 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 6:50 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-12 9:53 dpdklab
2024-04-12 9:51 dpdklab
2024-04-12 9:16 dpdklab
2024-04-12 8:16 dpdklab
2024-04-12 8:02 dpdklab
2024-04-12 7:56 dpdklab
2024-04-12 7:53 dpdklab
2024-04-12 7:48 dpdklab
2024-04-12 7:46 dpdklab
2024-04-12 7:44 dpdklab
2024-04-12 7:20 dpdklab
2024-04-12 7:18 dpdklab
2024-04-12 7:17 dpdklab
2024-04-12 7:11 dpdklab
2024-04-12 7:06 dpdklab
2024-04-12 7:05 dpdklab
2024-04-12 7:04 dpdklab
2024-04-12 7:04 dpdklab
2024-04-12 7:03 dpdklab
2024-04-12 7:03 dpdklab
2024-04-12 7:03 dpdklab
2024-04-12 7:03 dpdklab
2024-04-12 7:03 dpdklab
2024-04-12 7:03 dpdklab
2024-04-12 7:03 dpdklab
2024-04-12 7:02 dpdklab
2024-04-12 7:02 dpdklab
2024-04-12 7:02 dpdklab
2024-04-12 7:02 dpdklab
2024-04-12 7:02 dpdklab
2024-04-12 7:01 dpdklab
2024-04-12 7:01 dpdklab
2024-04-12 7:01 dpdklab
2024-04-12 7:01 dpdklab
2024-04-12 7:01 dpdklab
2024-04-12 7:00 dpdklab
2024-04-12 7:00 dpdklab
2024-04-12 7:00 dpdklab
2024-04-12 7:00 dpdklab
2024-04-12 7:00 dpdklab
2024-04-12 7:00 dpdklab
2024-04-12 7:00 dpdklab
2024-04-12 6:59 dpdklab
2024-04-12 6:59 dpdklab
2024-04-12 6:59 dpdklab
2024-04-12 6:59 dpdklab
2024-04-12 6:59 dpdklab
2024-04-12 6:58 dpdklab
2024-04-12 6:58 dpdklab
2024-04-12 6:58 dpdklab
2024-04-12 6:58 dpdklab
2024-04-12 6:58 dpdklab
2024-04-12 6:58 dpdklab
2024-04-12 6:58 dpdklab
2024-04-12 6:58 dpdklab
2024-04-12 6:58 dpdklab
2024-04-12 6:57 dpdklab
2024-04-12 6:57 dpdklab
2024-04-12 6:57 dpdklab
2024-04-12 6:57 dpdklab
2024-04-12 6:57 dpdklab
2024-04-12 6:56 dpdklab
2024-04-12 6:56 dpdklab
2024-04-12 6:56 dpdklab
2024-04-12 6:56 dpdklab
2024-04-12 6:56 dpdklab
2024-04-12 6:55 dpdklab
2024-04-12 6:55 dpdklab
2024-04-12 6:55 dpdklab
2024-04-12 6:55 dpdklab
2024-04-12 6:55 dpdklab
2024-04-12 6:54 dpdklab
2024-04-12 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=6618d9ba.0d0a0220.29aae.b089SMTPIN_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).