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] 8effaffad34e015bb83f10e7d91617a6d4043f04
Date: Thu, 03 Apr 2025 00:34:17 -0700 (PDT) [thread overview]
Message-ID: <67ee39f9.170a0220.1176eb.20edSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: tags/v22.11
8effaffad34e015bb83f10e7d91617a6d4043f04 --> testing pass
Upstream job id: Generic-Unit-Test-DPDK#328512
Test environment and result as below:
+-----------------------------+----------------+---------------------------+------------------------------+--------------+
| Environment | dpdk_unit_test | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | lpm_autotest |
+=============================+================+===========================+==============================+==============+
| 32-bit Ubuntu 22.04.4 (ARM) | PASS | SKIPPED | SKIPPED | SKIPPED |
+-----------------------------+----------------+---------------------------+------------------------------+--------------+
| Debian 12 (arm) | SKIPPED | PASS | PASS | SKIPPED |
+-----------------------------+----------------+---------------------------+------------------------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | SKIPPED | SKIPPED | PASS |
+-----------------------------+----------------+---------------------------+------------------------------+--------------+
32-bit Ubuntu 22.04.4 (ARM)
Kernel: 5.15.83+ aarch64
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Debian 12 (arm)
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Ubuntu 20.04 ARM SVE
Kernel: Depends on container host
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/33139/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-04-03 7:34 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 7:34 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-04 17:40 dpdklab
2025-04-04 16:12 dpdklab
2025-04-04 8:34 dpdklab
2025-04-04 8:05 dpdklab
2025-04-04 7:25 dpdklab
2025-04-04 7:25 dpdklab
2025-04-04 7:00 dpdklab
2025-04-04 6:04 dpdklab
2025-04-04 6:03 dpdklab
2025-04-04 5:40 dpdklab
2025-04-04 5:31 dpdklab
2025-04-04 5:27 dpdklab
2025-04-04 5:10 dpdklab
2025-04-04 4:40 dpdklab
2025-04-03 22:34 dpdklab
2025-04-03 22:13 dpdklab
2025-04-03 11:00 dpdklab
2025-04-03 7:29 dpdklab
2025-04-03 6:42 dpdklab
2025-04-03 5:13 dpdklab
2025-04-03 5:12 dpdklab
2025-04-03 5:02 dpdklab
2025-04-03 4:56 dpdklab
2025-04-03 4:51 dpdklab
2025-04-02 10:04 dpdklab
2025-04-02 8:31 dpdklab
2025-04-02 7:25 dpdklab
2025-04-02 6:52 dpdklab
2025-04-02 6:22 dpdklab
2025-04-02 6:16 dpdklab
2025-04-02 6:06 dpdklab
2025-04-02 6:01 dpdklab
2025-04-02 5:34 dpdklab
2025-04-02 5:29 dpdklab
2025-04-02 4:38 dpdklab
2025-04-02 4:36 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=67ee39f9.170a0220.1176eb.20edSMTPIN_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).