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] 99dcd1664982fd93d49ca159a97ad16537a1914f
Date: Mon, 16 Oct 2023 11:41:50 -0700 (PDT) [thread overview]
Message-ID: <652d83ee.4a0a0220.6ff74.d7c9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
99dcd1664982fd93d49ca159a97ad16537a1914f --> 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 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/26497/
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-16 18:41 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 18:41 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-18 1:45 dpdklab
2023-10-18 1:41 dpdklab
2023-10-16 23:13 dpdklab
2023-10-16 23:03 dpdklab
2023-10-16 21:45 dpdklab
2023-10-16 19:59 dpdklab
2023-10-16 19:49 dpdklab
2023-10-16 19:47 dpdklab
2023-10-16 19:47 dpdklab
2023-10-16 19:43 dpdklab
2023-10-16 19:25 dpdklab
2023-10-16 19:14 dpdklab
2023-10-16 19:08 dpdklab
2023-10-16 19:07 dpdklab
2023-10-16 19:06 dpdklab
2023-10-16 19:01 dpdklab
2023-10-16 18:59 dpdklab
2023-10-16 18:58 dpdklab
2023-10-16 18:56 dpdklab
2023-10-16 18:55 dpdklab
2023-10-16 18:54 dpdklab
2023-10-16 18:51 dpdklab
2023-10-16 18:51 dpdklab
2023-10-16 18:49 dpdklab
2023-10-16 18:49 dpdklab
2023-10-16 18:48 dpdklab
2023-10-16 18:48 dpdklab
2023-10-16 18:47 dpdklab
2023-10-16 18:46 dpdklab
2023-10-16 18:46 dpdklab
2023-10-16 18:42 dpdklab
2023-10-16 18:41 dpdklab
2023-10-16 18:41 dpdklab
2023-10-16 18:39 dpdklab
2023-10-16 18:38 dpdklab
2023-10-16 18:37 dpdklab
2023-10-16 18:37 dpdklab
2023-10-16 18:37 dpdklab
2023-10-16 18:36 dpdklab
2023-10-16 18:35 dpdklab
2023-10-16 18:35 dpdklab
2023-10-16 18:34 dpdklab
2023-10-16 18:30 dpdklab
2023-10-16 18:30 dpdklab
2023-10-16 18:29 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=652d83ee.4a0a0220.6ff74.d7c9SMTPIN_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).