From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@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] 9fb53245eaa0b2ab22bb6e3650eda2a5746edc2f
Date: Thu, 10 Aug 2023 19:22:28 -0700 (PDT) [thread overview]
Message-ID: <64d59b64.170a0220.8f2a1.3d13SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: 22.11-staging
9fb53245eaa0b2ab22bb6e3650eda2a5746edc2f --> testing pass
Test environment and result as below:
+--------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+======================================+====================+
| Fedora 38 (ARM) | PASS |
+--------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+--------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+--------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+--------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+--------------------------------------+--------------------+
| Fedora 38 (ARM Clang) | PASS |
+--------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+--------------------------------------+--------------------+
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Fedora 38 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 16.0.3
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/25749/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-11 2:22 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 2:22 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 4:39 dpdklab
2023-08-14 4:39 dpdklab
2023-08-14 4:36 dpdklab
2023-08-14 4:36 dpdklab
2023-08-14 4:35 dpdklab
2023-08-14 4:35 dpdklab
2023-08-14 4:35 dpdklab
2023-08-14 4:33 dpdklab
2023-08-14 4:23 dpdklab
2023-08-14 4:20 dpdklab
2023-08-14 4:15 dpdklab
2023-08-14 4:15 dpdklab
2023-08-14 0:31 dpdklab
2023-08-13 19:34 dpdklab
2023-08-11 21:40 dpdklab
2023-08-11 21:28 dpdklab
2023-08-11 20:51 dpdklab
2023-08-11 20:03 dpdklab
2023-08-11 20:02 dpdklab
2023-08-11 20:02 dpdklab
2023-08-11 20:02 dpdklab
2023-08-11 17:44 dpdklab
2023-08-11 2:24 dpdklab
2023-08-11 2:23 dpdklab
2023-08-11 2:21 dpdklab
2023-08-11 2:21 dpdklab
2023-08-11 2:20 dpdklab
2023-08-11 2:20 dpdklab
2023-08-11 2:19 dpdklab
2023-08-11 2:14 dpdklab
2023-08-11 2:14 dpdklab
2023-08-11 2:13 dpdklab
2023-08-11 2:12 dpdklab
2023-08-11 2:12 dpdklab
2023-08-11 2:11 dpdklab
2023-08-11 2:10 dpdklab
2023-08-11 2:08 dpdklab
2023-08-11 2:08 dpdklab
2023-08-11 2:08 dpdklab
2023-08-11 2:06 dpdklab
2023-08-11 2:04 dpdklab
2023-08-11 2:03 dpdklab
2023-08-11 2:02 dpdklab
2023-08-11 2:01 dpdklab
2023-08-11 1:51 dpdklab
2023-08-11 1:09 dpdklab
2023-08-11 1:08 dpdklab
2023-08-11 1:04 dpdklab
2023-08-11 1:03 dpdklab
2023-08-11 0:56 dpdklab
2023-08-11 0:30 dpdklab
2023-08-10 2:09 dpdklab
2023-08-10 1:49 dpdklab
2023-08-10 1:17 dpdklab
2023-08-10 1:03 dpdklab
2023-08-10 0:55 dpdklab
2023-08-10 0:41 dpdklab
2023-08-10 0:36 dpdklab
2023-08-10 0:20 dpdklab
2023-08-10 0:20 dpdklab
2023-08-10 0:14 dpdklab
2023-08-10 0:12 dpdklab
2023-08-10 0:12 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=64d59b64.170a0220.8f2a1.3d13SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dpdk-test-reports@iol.unh.edu \
--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).