From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] d7b8b11866a7c4b5975eaedd15dcc9a6f0cd92ce
Date: Wed, 18 Oct 2023 18:12:37 -0700 (PDT) [thread overview]
Message-ID: <65308285.050a0220.c7f16.40f2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
d7b8b11866a7c4b5975eaedd15dcc9a6f0cd92ce --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
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 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 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/26545/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-19 1:12 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 1:12 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-19 18:08 dpdklab
2023-10-19 18:03 dpdklab
2023-10-19 18:03 dpdklab
2023-10-19 18:02 dpdklab
2023-10-19 18:01 dpdklab
2023-10-19 18:01 dpdklab
2023-10-19 18:00 dpdklab
2023-10-19 18:00 dpdklab
2023-10-19 17:59 dpdklab
2023-10-19 17:59 dpdklab
2023-10-19 17:58 dpdklab
2023-10-19 17:52 dpdklab
2023-10-19 17:52 dpdklab
2023-10-19 17:51 dpdklab
2023-10-19 17:50 dpdklab
2023-10-19 17:49 dpdklab
2023-10-19 16:32 dpdklab
2023-10-19 16:25 dpdklab
2023-10-19 16:12 dpdklab
2023-10-19 16:09 dpdklab
2023-10-19 16:08 dpdklab
2023-10-19 16:04 dpdklab
2023-10-19 16:03 dpdklab
2023-10-19 16:00 dpdklab
2023-10-19 15:59 dpdklab
2023-10-19 15:57 dpdklab
2023-10-19 15:57 dpdklab
2023-10-19 15:55 dpdklab
2023-10-19 15:55 dpdklab
2023-10-19 15:54 dpdklab
2023-10-19 15:53 dpdklab
2023-10-19 15:52 dpdklab
2023-10-19 15:50 dpdklab
2023-10-19 15:48 dpdklab
2023-10-19 15:46 dpdklab
2023-10-19 15:46 dpdklab
2023-10-19 15:44 dpdklab
2023-10-19 2:34 dpdklab
2023-10-19 1:32 dpdklab
2023-10-19 1:26 dpdklab
2023-10-19 1:24 dpdklab
2023-10-19 1:24 dpdklab
2023-10-19 1:22 dpdklab
2023-10-19 1:21 dpdklab
2023-10-19 1:20 dpdklab
2023-10-19 1:20 dpdklab
2023-10-19 1:20 dpdklab
2023-10-19 1:20 dpdklab
2023-10-19 1:18 dpdklab
2023-10-19 1:18 dpdklab
2023-10-19 1:18 dpdklab
2023-10-19 1:17 dpdklab
2023-10-19 1:17 dpdklab
2023-10-19 1:16 dpdklab
2023-10-19 1:16 dpdklab
2023-10-19 1:15 dpdklab
2023-10-19 1:15 dpdklab
2023-10-19 1:15 dpdklab
2023-10-19 1:15 dpdklab
2023-10-19 1:15 dpdklab
2023-10-19 1:15 dpdklab
2023-10-19 1:14 dpdklab
2023-10-19 1:14 dpdklab
2023-10-19 1:13 dpdklab
2023-10-19 1:13 dpdklab
2023-10-19 1:13 dpdklab
2023-10-19 1:13 dpdklab
2023-10-19 1:13 dpdklab
2023-10-19 1:12 dpdklab
2023-10-19 1:12 dpdklab
2023-10-19 1:12 dpdklab
2023-10-19 1:12 dpdklab
2023-10-19 1:11 dpdklab
2023-10-19 1:11 dpdklab
2023-10-19 1:11 dpdklab
2023-10-19 1:11 dpdklab
2023-10-19 1:10 dpdklab
2023-10-19 1:10 dpdklab
2023-10-19 1:10 dpdklab
2023-10-19 1:10 dpdklab
2023-10-19 1:10 dpdklab
2023-10-19 1:10 dpdklab
2023-10-19 1:09 dpdklab
2023-10-19 1:09 dpdklab
2023-10-19 1: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=65308285.050a0220.c7f16.40f2SMTPIN_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).