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] cdb53b339ba0956f98c21f0aed2685c74d4ef9ea
Date: Mon, 31 Jul 2023 02:55:46 -0700 (PDT) [thread overview]
Message-ID: <64c78522.050a0220.1317f.8076SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: 21.11-staging
cdb53b339ba0956f98c21f0aed2685c74d4ef9ea --> testing pass
Test environment and result as below:
+-----------------------------+--------------+----------------+
| Environment | lpm_autotest | dpdk_unit_test |
+=============================+==============+================+
| Ubuntu 20.04 ARM SVE | PASS | SKIPPED |
+-----------------------------+--------------+----------------+
| (32-bit) ARM Ubuntu 20.04.4 | SKIPPED | PASS |
+-----------------------------+--------------+----------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
(32-bit) ARM Ubuntu 20.04.4
Kernel: 5.4.0-148-generic aarch64
Compiler: gcc 9.4
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/25642/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-07-31 9:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 9:55 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-31 18:53 dpdklab
2023-07-31 12:21 dpdklab
2023-07-31 12:15 dpdklab
2023-07-31 12:09 dpdklab
2023-07-31 11:03 dpdklab
2023-07-31 10:55 dpdklab
2023-07-31 10:23 dpdklab
2023-07-31 9:43 dpdklab
2023-07-31 9:42 dpdklab
2023-07-31 9:42 dpdklab
2023-07-31 9:41 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=64c78522.050a0220.1317f.8076SMTPIN_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).