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] a871dfd632b3a3973095beb76ddcfdf61e8e14fb
Date: Wed, 11 Oct 2023 01:49:59 -0700 (PDT) [thread overview]
Message-ID: <652661b7.920a0220.ed4ad.bea0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net-intel
a871dfd632b3a3973095beb76ddcfdf61e8e14fb --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| CentOS Stream 9 (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)
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.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/26431/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-11 8:50 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 8:49 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-12 14:41 dpdklab
2023-10-12 7:05 dpdklab
2023-10-12 7:03 dpdklab
2023-10-12 7:02 dpdklab
2023-10-11 14:14 dpdklab
2023-10-11 10:22 dpdklab
2023-10-11 9:47 dpdklab
2023-10-11 9:36 dpdklab
2023-10-11 9:34 dpdklab
2023-10-11 9:16 dpdklab
2023-10-11 9:08 dpdklab
2023-10-11 9:08 dpdklab
2023-10-11 9:07 dpdklab
2023-10-11 9:06 dpdklab
2023-10-11 9:05 dpdklab
2023-10-11 9:03 dpdklab
2023-10-11 8:57 dpdklab
2023-10-11 8:56 dpdklab
2023-10-11 8:56 dpdklab
2023-10-11 8:56 dpdklab
2023-10-11 8:56 dpdklab
2023-10-11 8:55 dpdklab
2023-10-11 8:55 dpdklab
2023-10-11 8:54 dpdklab
2023-10-11 8:53 dpdklab
2023-10-11 8:53 dpdklab
2023-10-11 8:40 dpdklab
2023-10-11 8:34 dpdklab
2023-10-11 8:33 dpdklab
2023-10-11 8:29 dpdklab
2023-10-11 8:27 dpdklab
2023-10-11 8:26 dpdklab
2023-10-11 8:24 dpdklab
2023-10-11 8:23 dpdklab
2023-10-11 8:22 dpdklab
2023-10-11 8:21 dpdklab
2023-10-11 8:19 dpdklab
2023-10-11 8:13 dpdklab
2023-10-11 8:08 dpdklab
2023-10-11 8:05 dpdklab
2023-10-11 2:12 dpdklab
2023-10-11 0:48 dpdklab
2023-10-11 0:43 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=652661b7.920a0220.ed4ad.bea0SMTPIN_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).