From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 62b906cf06ba86adf1f05c16969a9adcc49cf8bc
Date: Thu, 15 Feb 2024 17:25:16 -0800 (PST) [thread overview]
Message-ID: <65ceb97c.920a0220.6fb14.1ebaSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
62b906cf06ba86adf1f05c16969a9adcc49cf8bc --> testing pass
Test environment and result as below:
+-----------------------+--------------------+
| Environment | dpdk_meson_compile |
+=======================+====================+
| Fedora 38 (ARM) | PASS |
+-----------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+-----------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+-----------------------+--------------------+
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
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/28026/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-16 1:25 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 1:25 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-16 3:02 dpdklab
2024-02-16 3:00 dpdklab
2024-02-16 2:56 dpdklab
2024-02-16 2:40 dpdklab
2024-02-16 2:20 dpdklab
2024-02-16 2:19 dpdklab
2024-02-16 2:03 dpdklab
2024-02-16 2:01 dpdklab
2024-02-16 1:51 dpdklab
2024-02-16 1:50 dpdklab
2024-02-16 1:49 dpdklab
2024-02-16 1:48 dpdklab
2024-02-16 1:47 dpdklab
2024-02-16 1:45 dpdklab
2024-02-16 1:45 dpdklab
2024-02-16 1:45 dpdklab
2024-02-16 1:45 dpdklab
2024-02-16 1:45 dpdklab
2024-02-16 1:44 dpdklab
2024-02-16 1:42 dpdklab
2024-02-16 1:41 dpdklab
2024-02-16 1:40 dpdklab
2024-02-16 1:39 dpdklab
2024-02-16 1:38 dpdklab
2024-02-16 1:37 dpdklab
2024-02-16 1:37 dpdklab
2024-02-16 1:37 dpdklab
2024-02-16 1:36 dpdklab
2024-02-16 1:36 dpdklab
2024-02-16 1:36 dpdklab
2024-02-16 1:35 dpdklab
2024-02-16 1:34 dpdklab
2024-02-16 1:34 dpdklab
2024-02-16 1:33 dpdklab
2024-02-16 1:33 dpdklab
2024-02-16 1:32 dpdklab
2024-02-16 1:29 dpdklab
2024-02-16 1:29 dpdklab
2024-02-16 1:29 dpdklab
2024-02-16 1:28 dpdklab
2024-02-16 1:27 dpdklab
2024-02-16 1:27 dpdklab
2024-02-16 1:27 dpdklab
2024-02-16 1:27 dpdklab
2024-02-16 1:27 dpdklab
2024-02-16 1:27 dpdklab
2024-02-16 1:27 dpdklab
2024-02-16 1:27 dpdklab
2024-02-16 1:26 dpdklab
2024-02-16 1:26 dpdklab
2024-02-16 1:25 dpdklab
2024-02-16 1:24 dpdklab
2024-02-16 1:24 dpdklab
2024-02-16 1:24 dpdklab
2024-02-16 1:24 dpdklab
2024-02-16 1:23 dpdklab
2024-02-16 1:23 dpdklab
2024-02-16 1:22 dpdklab
2024-02-16 1:22 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=65ceb97c.920a0220.6fb14.1ebaSMTPIN_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).