From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 34c0c38ab772e8eea5243f530866d5b68519e7c7
Date: Fri, 03 Nov 2023 19:23:54 -0700 (PDT) [thread overview]
Message-ID: <6545ab3a.250a0220.f6bb6.8429SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
34c0c38ab772e8eea5243f530866d5b68519e7c7 --> 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 ARM Clang Cross Compile | PASS |
+--------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+--------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+--------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+--------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+--------------------------------------+--------------------+
| Fedora 38 (ARM) | 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 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/26826/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-04 2:23 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 2:23 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-04 9:42 dpdklab
2023-11-04 3:32 dpdklab
2023-11-04 3:26 dpdklab
2023-11-04 3:23 dpdklab
2023-11-04 3:00 dpdklab
2023-11-04 2:50 dpdklab
2023-11-04 2:30 dpdklab
2023-11-04 2:30 dpdklab
2023-11-04 2:27 dpdklab
2023-11-04 2:27 dpdklab
2023-11-04 2:26 dpdklab
2023-11-04 2:26 dpdklab
2023-11-04 2:26 dpdklab
2023-11-04 2:26 dpdklab
2023-11-04 2:26 dpdklab
2023-11-04 2:25 dpdklab
2023-11-04 2:25 dpdklab
2023-11-04 2:25 dpdklab
2023-11-04 2:25 dpdklab
2023-11-04 2:25 dpdklab
2023-11-04 2:24 dpdklab
2023-11-04 2:24 dpdklab
2023-11-04 2:24 dpdklab
2023-11-04 2:24 dpdklab
2023-11-04 2:24 dpdklab
2023-11-04 2:23 dpdklab
2023-11-04 2:23 dpdklab
2023-11-04 2:22 dpdklab
2023-11-04 2:22 dpdklab
2023-11-04 2:21 dpdklab
2023-11-04 2:21 dpdklab
2023-11-04 2:21 dpdklab
2023-11-04 2:20 dpdklab
2023-11-04 2:20 dpdklab
2023-11-04 2:20 dpdklab
2023-11-04 2:19 dpdklab
2023-11-04 2:19 dpdklab
2023-11-04 2:18 dpdklab
2023-11-04 2:18 dpdklab
2023-11-04 2:18 dpdklab
2023-11-04 2:17 dpdklab
2023-11-04 2:17 dpdklab
2023-11-04 2:17 dpdklab
2023-11-04 2:17 dpdklab
2023-11-04 2:17 dpdklab
2023-11-04 2:17 dpdklab
2023-11-04 2:15 dpdklab
2023-11-04 2:15 dpdklab
2023-11-04 2:14 dpdklab
2023-11-04 2:13 dpdklab
2023-11-04 2:13 dpdklab
2023-11-04 2:13 dpdklab
2023-11-04 2:10 dpdklab
2023-11-04 2:10 dpdklab
2023-11-04 1:54 dpdklab
2023-11-04 1:49 dpdklab
2023-11-04 1:39 dpdklab
2023-11-04 1:39 dpdklab
2023-11-04 1:37 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=6545ab3a.250a0220.f6bb6.8429SMTPIN_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).