From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Qi Zhang <qi.z.zhang@intel.com>
Subject: |SUCCESS| [GIT MASTER] 915ecb9cd68c5d613bee44ad41536a4f489f6d15
Date: Thu, 04 Jan 2024 14:07:54 -0800 (PST) [thread overview]
Message-ID: <65972c3a.4a0a0220.5dbe8.0e58SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net-intel
915ecb9cd68c5d613bee44ad41536a4f489f6d15 --> 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 |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC 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 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
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27562/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-04 22:07 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 22:07 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-05 8:27 dpdklab
2024-01-05 8:18 dpdklab
2024-01-05 0:55 dpdklab
2024-01-05 0:49 dpdklab
2024-01-04 23:34 dpdklab
2024-01-04 23:16 dpdklab
2024-01-04 22:32 dpdklab
2024-01-04 22:25 dpdklab
2024-01-04 22:23 dpdklab
2024-01-04 22:19 dpdklab
2024-01-04 22:19 dpdklab
2024-01-04 22:18 dpdklab
2024-01-04 22:16 dpdklab
2024-01-04 22:15 dpdklab
2024-01-04 22:15 dpdklab
2024-01-04 22:14 dpdklab
2024-01-04 22:14 dpdklab
2024-01-04 22:13 dpdklab
2024-01-04 22:11 dpdklab
2024-01-04 22:10 dpdklab
2024-01-04 22:10 dpdklab
2024-01-04 22:10 dpdklab
2024-01-04 22:10 dpdklab
2024-01-04 22:10 dpdklab
2024-01-04 22:09 dpdklab
2024-01-04 22:08 dpdklab
2024-01-04 22:08 dpdklab
2024-01-04 22:08 dpdklab
2024-01-04 22:06 dpdklab
2024-01-04 22:06 dpdklab
2024-01-04 22:05 dpdklab
2024-01-04 22:03 dpdklab
2024-01-04 22:03 dpdklab
2024-01-04 22:02 dpdklab
2024-01-04 22:02 dpdklab
2024-01-04 22:01 dpdklab
2024-01-04 22:01 dpdklab
2024-01-04 22:00 dpdklab
2024-01-04 22:00 dpdklab
2024-01-04 22:00 dpdklab
2024-01-04 21:59 dpdklab
2024-01-04 21:57 dpdklab
2024-01-04 21:47 dpdklab
2024-01-04 21:46 dpdklab
2024-01-04 21:45 dpdklab
2024-01-04 21:44 dpdklab
2024-01-04 21:43 dpdklab
2024-01-04 21:42 dpdklab
2024-01-04 21:39 dpdklab
2024-01-04 21:38 dpdklab
2024-01-04 21:38 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=65972c3a.4a0a0220.5dbe8.0e58SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=qi.z.zhang@intel.com \
--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).