From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] d3564c17132748bad38fa7bd4e0c870012b5bae0
Date: Wed, 26 Jun 2024 07:36:23 -0700 (PDT) [thread overview]
Message-ID: <667c2767.050a0220.9102b.f181SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net-intel
d3564c17132748bad38fa7bd4e0c870012b5bae0 --> testing pass
Test environment and result as below:
+----------------------+--------------------+
| Environment | dpdk_meson_compile |
+======================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------+--------------------+
| Debian 12 with MUSDK | PASS |
+----------------------+--------------------+
| RHEL9 (ARM) | PASS |
+----------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+----------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------+--------------------+
| Fedora 39 (ARM) | PASS |
+----------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+----------------------+--------------------+
| Debian 12 (arm) | PASS |
+----------------------+--------------------+
| Fedora 40 (ARM) | PASS |
+----------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-167-generic
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
Debian 12 with MUSDK
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
RHEL9 (ARM)
Kernel: Depends on container host
Compiler: gcc 11.4.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Fedora 39 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Fedora 40 (ARM)
Kernel: Depends on container host
Compiler: gcc 14.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29593/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-06-26 14:36 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 14:36 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-27 5:54 dpdklab
2024-06-27 2:23 dpdklab
2024-06-27 0:44 dpdklab
2024-06-26 20:24 dpdklab
2024-06-26 16:56 dpdklab
2024-06-26 16:43 dpdklab
2024-06-26 16:26 dpdklab
2024-06-26 16:25 dpdklab
2024-06-26 16:18 dpdklab
2024-06-26 16:16 dpdklab
2024-06-26 16:11 dpdklab
2024-06-26 15:35 dpdklab
2024-06-26 15:34 dpdklab
2024-06-26 15:34 dpdklab
2024-06-26 15:33 dpdklab
2024-06-26 15:32 dpdklab
2024-06-26 15:29 dpdklab
2024-06-26 15:27 dpdklab
2024-06-26 15:13 dpdklab
2024-06-26 15:11 dpdklab
2024-06-26 15:10 dpdklab
2024-06-26 15:06 dpdklab
2024-06-26 15:06 dpdklab
2024-06-26 15:05 dpdklab
2024-06-26 15:04 dpdklab
2024-06-26 15:04 dpdklab
2024-06-26 15:04 dpdklab
2024-06-26 14:59 dpdklab
2024-06-26 14:59 dpdklab
2024-06-26 14:58 dpdklab
2024-06-26 14:38 dpdklab
2024-06-26 14:36 dpdklab
2024-06-26 14:36 dpdklab
2024-06-26 14:35 dpdklab
2024-06-26 14:34 dpdklab
2024-06-26 14:33 dpdklab
2024-06-26 14:32 dpdklab
2024-06-26 14:31 dpdklab
2024-06-26 14:31 dpdklab
2024-06-26 14:29 dpdklab
2024-06-26 14:28 dpdklab
2024-06-26 13:18 dpdklab
2024-06-26 13:09 dpdklab
2024-06-26 13:06 dpdklab
2024-06-26 13:05 dpdklab
2024-06-26 13:03 dpdklab
2024-06-26 12:57 dpdklab
2024-06-26 12:57 dpdklab
2024-06-26 12:56 dpdklab
2024-06-26 12:55 dpdklab
2024-06-26 12:55 dpdklab
2024-06-26 12:54 dpdklab
2024-06-26 12:54 dpdklab
2024-06-26 12:48 dpdklab
2024-06-26 12:46 dpdklab
2024-06-26 12:46 dpdklab
2024-06-26 12:46 dpdklab
2024-06-26 12:42 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=667c2767.050a0220.9102b.f181SMTPIN_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).