From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] dccd6b7c68116a1cc044856aa35928e044640a8d
Date: Thu, 15 Feb 2024 01:25:46 -0800 (PST) [thread overview]
Message-ID: <65cdd89a.250a0220.2d470d.0956SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
dccd6b7c68116a1cc044856aa35928e044640a8d --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang 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 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28016/
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-15 9:25 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 9:25 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-15 12:35 dpdklab
2024-02-15 12:25 dpdklab
2024-02-15 12:07 dpdklab
2024-02-15 11:50 dpdklab
2024-02-15 11:47 dpdklab
2024-02-15 10:41 dpdklab
2024-02-15 10:02 dpdklab
2024-02-15 9:58 dpdklab
2024-02-15 9:58 dpdklab
2024-02-15 9:54 dpdklab
2024-02-15 9:54 dpdklab
2024-02-15 9:50 dpdklab
2024-02-15 9:34 dpdklab
2024-02-15 9:16 dpdklab
2024-02-15 9:15 dpdklab
2024-02-15 9:14 dpdklab
2024-02-15 9:11 dpdklab
2024-02-15 9:08 dpdklab
2024-02-15 9:07 dpdklab
2024-02-15 9:07 dpdklab
2024-02-15 9:07 dpdklab
2024-02-15 9:06 dpdklab
2024-02-15 9:03 dpdklab
2024-02-15 9:03 dpdklab
2024-02-15 9:02 dpdklab
2024-02-15 9:01 dpdklab
2024-02-15 9:00 dpdklab
2024-02-15 8:58 dpdklab
2024-02-15 8:58 dpdklab
2024-02-15 8:57 dpdklab
2024-02-15 8:57 dpdklab
2024-02-15 8:56 dpdklab
2024-02-15 8:55 dpdklab
2024-02-15 8:54 dpdklab
2024-02-15 8:47 dpdklab
2024-02-15 8:38 dpdklab
2024-02-15 8:33 dpdklab
2024-02-15 8:19 dpdklab
2024-02-15 8:19 dpdklab
2024-02-15 8:16 dpdklab
2024-02-15 8:14 dpdklab
2024-02-15 8:14 dpdklab
2024-02-15 8:12 dpdklab
2024-02-15 8:02 dpdklab
2024-02-15 8:01 dpdklab
2024-02-15 8:00 dpdklab
2024-02-15 7:59 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=65cdd89a.250a0220.2d470d.0956SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@amd.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).