From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| [GIT MASTER] 4aee6110bb10b0225fa9562f2e48af233a9058a1
Date: Tue, 6 Sep 2022 21:58:07 +0000 (UTC) [thread overview]
Message-ID: <20220906215807.78204601C4@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1906 bytes --]
_Testing PASS_
Branch: dpdk
4aee6110bb10b0225fa9562f2e48af233a9058a1 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Native | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Native | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 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)
Ubuntu 20.04 ARM GCC Native
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
Ubuntu 20.04 ARM Clang Native
Kernel: 5.4.0-53-generic
Compiler: clang 10.0.0-4ubuntu1
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/21258/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-09-06 21:58 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 21:58 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-09 16:54 dpdklab
2022-09-09 16:40 dpdklab
2022-09-09 16:32 dpdklab
2022-09-09 16:19 dpdklab
2022-09-09 16:18 dpdklab
2022-09-09 16:12 dpdklab
2022-09-09 16:02 dpdklab
2022-09-09 16:02 dpdklab
2022-09-09 15:56 dpdklab
2022-09-09 15:55 dpdklab
2022-09-06 21:55 dpdklab
2022-09-06 21:54 dpdklab
2022-09-06 21:51 dpdklab
2022-09-06 21:41 dpdklab
2022-09-06 21:39 dpdklab
2022-09-06 21:37 dpdklab
2022-09-06 21:36 dpdklab
2022-09-06 21:35 dpdklab
2022-09-06 21:31 dpdklab
2022-09-06 16:07 dpdklab
2022-09-06 16:05 dpdklab
2022-09-06 16:03 dpdklab
2022-09-06 15:54 dpdklab
2022-09-06 15:53 dpdklab
2022-09-06 15:49 dpdklab
2022-09-06 15:48 dpdklab
2022-09-06 15:48 dpdklab
2022-09-06 15:47 dpdklab
2022-09-06 15:41 dpdklab
2022-08-29 21:03 dpdklab
2022-08-29 21:01 dpdklab
2022-08-29 20:56 dpdklab
2022-08-29 20:48 dpdklab
2022-08-29 20:44 dpdklab
2022-08-29 20:42 dpdklab
2022-08-29 20:42 dpdklab
2022-08-29 20:36 dpdklab
2022-08-29 20:34 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=20220906215807.78204601C4@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).