From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@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] 74f84c75584a043cbc7f983579083f01f8b7d225
Date: Wed, 1 Mar 2023 16:37:48 +0000 (UTC) [thread overview]
Message-ID: <20230301163748.B1A01601B1@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
_Testing PASS_
Branch: 21.11-staging
74f84c75584a043cbc7f983579083f01f8b7d225 --> testing pass
Test environment and result as below:
+------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+====================================+====================+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+------------------------------------+--------------------+
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
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/23560/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-01 16:37 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 16:37 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-02 7:00 dpdklab
2023-03-02 6:59 dpdklab
2023-03-02 6:55 dpdklab
2023-03-02 6:53 dpdklab
2023-03-02 6:50 dpdklab
2023-03-02 6:46 dpdklab
2023-03-02 6:46 dpdklab
2023-03-02 6:45 dpdklab
2023-03-02 6:38 dpdklab
2023-03-02 6:35 dpdklab
2023-03-02 6:33 dpdklab
2023-03-01 17:18 dpdklab
2023-03-01 13:22 dpdklab
2023-03-01 13:09 dpdklab
2023-03-01 11:25 dpdklab
2023-03-01 11:13 dpdklab
2023-03-01 10:20 dpdklab
2023-03-01 10:14 dpdklab
2023-03-01 10:10 dpdklab
2023-03-01 10:09 dpdklab
2023-03-01 10:08 dpdklab
2023-03-01 10:04 dpdklab
2023-03-01 10:04 dpdklab
2023-03-01 10:02 dpdklab
2023-03-01 9:58 dpdklab
2023-02-23 15:56 dpdklab
2023-02-23 15:55 dpdklab
2023-02-23 15:51 dpdklab
2023-02-23 15:50 dpdklab
2023-02-23 15:45 dpdklab
2023-02-23 15:43 dpdklab
2023-02-23 15:35 dpdklab
2023-02-23 15:34 dpdklab
2023-02-23 15:31 dpdklab
2023-02-23 15:22 dpdklab
2023-02-23 15:20 dpdklab
2023-02-23 15:19 dpdklab
2023-02-23 15:16 dpdklab
2023-02-23 15:15 dpdklab
2023-02-23 15:04 dpdklab
2023-02-23 15:03 dpdklab
2023-02-23 15:00 dpdklab
2023-02-23 14:58 dpdklab
2023-02-23 14:53 dpdklab
2023-02-23 14:52 dpdklab
2023-02-23 2:18 dpdklab
2023-02-22 21:34 dpdklab
2023-02-22 21:34 dpdklab
2023-02-22 21:33 dpdklab
2023-02-22 21:31 dpdklab
2023-02-22 21:29 dpdklab
2023-02-22 21:29 dpdklab
2023-02-22 21:27 dpdklab
2023-02-22 21:21 dpdklab
2023-02-22 21:16 dpdklab
2023-02-22 21:02 dpdklab
2023-02-22 20:55 dpdklab
2023-02-22 18:37 dpdklab
2023-02-22 18:33 dpdklab
2023-02-22 18:31 dpdklab
2023-02-22 18:24 dpdklab
2023-02-22 18:21 dpdklab
2023-02-22 18:20 dpdklab
2023-02-22 18:18 dpdklab
2023-02-22 18:14 dpdklab
2023-02-22 18:10 dpdklab
2023-02-22 18:08 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=20230301163748.B1A01601B1@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--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).