From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] cd218549b686d6be394ef3b171eafa16c038bfe3
Date: Wed, 13 Mar 2024 17:30:46 -0700 (PDT) [thread overview]
Message-ID: <65f24536.050a0220.c017a.10b1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
cd218549b686d6be394ef3b171eafa16c038bfe3 --> testing pass
Test environment and result as below:
+----------------------+------------------------------+---------------------------+----------------+--------------+
| Environment | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest | dpdk_unit_test | lpm_autotest |
+======================+==============================+===========================+================+==============+
| Debian 12 (arm) | PASS | PASS | PASS | SKIPPED |
+----------------------+------------------------------+---------------------------+----------------+--------------+
| Fedora 37 (ARM) | SKIPPED | SKIPPED | PASS | SKIPPED |
+----------------------+------------------------------+---------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | SKIPPED | SKIPPED | PASS |
+----------------------+------------------------------+---------------------------+----------------+--------------+
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28473/
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-14 0:30 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 0:30 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-17 14:07 dpdklab
2024-03-17 13:27 dpdklab
2024-03-14 1:44 dpdklab
2024-03-14 0:58 dpdklab
2024-03-14 0:56 dpdklab
2024-03-14 0:46 dpdklab
2024-03-14 0:43 dpdklab
2024-03-14 0:42 dpdklab
2024-03-14 0:42 dpdklab
2024-03-14 0:41 dpdklab
2024-03-14 0:41 dpdklab
2024-03-14 0:39 dpdklab
2024-03-14 0:39 dpdklab
2024-03-14 0:38 dpdklab
2024-03-14 0:37 dpdklab
2024-03-14 0:36 dpdklab
2024-03-14 0:36 dpdklab
2024-03-14 0:35 dpdklab
2024-03-14 0:35 dpdklab
2024-03-14 0:33 dpdklab
2024-03-14 0:33 dpdklab
2024-03-14 0:32 dpdklab
2024-03-14 0:32 dpdklab
2024-03-14 0:32 dpdklab
2024-03-14 0:31 dpdklab
2024-03-14 0:31 dpdklab
2024-03-14 0:31 dpdklab
2024-03-14 0:30 dpdklab
2024-03-14 0:30 dpdklab
2024-03-14 0:30 dpdklab
2024-03-14 0:30 dpdklab
2024-03-14 0:29 dpdklab
2024-03-14 0:29 dpdklab
2024-03-14 0:29 dpdklab
2024-03-14 0:29 dpdklab
2024-03-14 0:28 dpdklab
2024-03-14 0:28 dpdklab
2024-03-14 0:28 dpdklab
2024-03-14 0:28 dpdklab
2024-03-14 0:28 dpdklab
2024-03-14 0:27 dpdklab
2024-03-14 0:27 dpdklab
2024-03-14 0:27 dpdklab
2024-03-14 0:27 dpdklab
2024-03-14 0:27 dpdklab
2024-03-14 0:27 dpdklab
2024-03-14 0:27 dpdklab
2024-03-14 0:26 dpdklab
2024-03-14 0:26 dpdklab
2024-03-14 0:26 dpdklab
2024-03-14 0:26 dpdklab
2024-03-14 0:26 dpdklab
2024-03-14 0:25 dpdklab
2024-03-14 0:25 dpdklab
2024-03-14 0:25 dpdklab
2024-03-14 0:25 dpdklab
2024-03-14 0:25 dpdklab
2024-03-14 0:24 dpdklab
2024-03-14 0:24 dpdklab
2024-03-14 0:23 dpdklab
2024-03-14 0:23 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=65f24536.050a0220.c017a.10b1SMTPIN_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).