From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 4d47f374314997c7f0be9bb5e3f9f757b5ed15e5
Date: Thu, 20 Jan 2022 11:11:44 +0000 (UTC) [thread overview]
Message-ID: <20220120111144.EEFF8602B7@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]
_Testing PASS_
Branch: tags/v20.11
4d47f374314997c7f0be9bb5e3f9f757b5ed15e5 --> testing pass
Test environment and result as below:
+------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+====================================+====================+
| Ubuntu 20.04 ARM Clang Native | PASS |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Native | PASS |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+------------------------------------+--------------------+
Ubuntu 20.04 ARM Clang Native
Kernel: 5.4.0-53-generic
Compiler: clang 10.0.0-4ubuntu1
Ubuntu 20.04 ARM GCC Native
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
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/18355/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-01-20 11:11 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 11:11 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-21 13:11 dpdklab
2022-01-21 8:42 dpdklab
2022-01-21 6:43 dpdklab
2022-01-21 6:28 dpdklab
2022-01-21 6:20 dpdklab
2022-01-21 6:12 dpdklab
2022-01-21 6:04 dpdklab
2022-01-21 6:01 dpdklab
2022-01-21 5:59 dpdklab
2022-01-21 5:58 dpdklab
2022-01-21 5:56 dpdklab
2022-01-21 5:55 dpdklab
2022-01-21 5:50 dpdklab
2022-01-20 20:33 dpdklab
2022-01-20 6:39 dpdklab
2022-01-20 6:30 dpdklab
2022-01-20 6:19 dpdklab
2022-01-20 6:13 dpdklab
2022-01-20 6:12 dpdklab
2022-01-20 6:05 dpdklab
2022-01-20 6:05 dpdklab
2022-01-20 6:00 dpdklab
2022-01-20 6:00 dpdklab
2022-01-19 8:48 dpdklab
2022-01-19 6:37 dpdklab
2022-01-19 6:26 dpdklab
2022-01-19 6:19 dpdklab
2022-01-19 6:15 dpdklab
2022-01-19 6:03 dpdklab
2022-01-19 6:00 dpdklab
2022-01-19 5:59 dpdklab
2022-01-19 5:56 dpdklab
2022-01-19 5:54 dpdklab
2022-01-19 5:54 dpdklab
2022-01-19 5:48 dpdklab
2022-01-19 5:45 dpdklab
2022-01-18 8:32 dpdklab
2022-01-18 7:21 dpdklab
2022-01-18 7:19 dpdklab
2022-01-18 7:14 dpdklab
2022-01-18 6:45 dpdklab
2022-01-18 6:28 dpdklab
2022-01-18 6:12 dpdklab
2022-01-18 6:11 dpdklab
2022-01-18 6:09 dpdklab
2022-01-18 6:00 dpdklab
2022-01-18 6:00 dpdklab
2022-01-18 5:57 dpdklab
2022-01-18 5:56 dpdklab
2022-01-17 13:19 dpdklab
2022-01-17 12:38 dpdklab
2022-01-17 12:32 dpdklab
2022-01-17 12:24 dpdklab
2022-01-17 12:03 dpdklab
2022-01-17 12:02 dpdklab
2022-01-17 11:59 dpdklab
2022-01-17 11:58 dpdklab
2022-01-17 11:54 dpdklab
2022-01-17 11:49 dpdklab
2022-01-17 11:49 dpdklab
2022-01-17 11:46 dpdklab
2022-01-17 11:46 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=20220120111144.EEFF8602B7@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@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).