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] 8e5cbd3d1f6f077abdcb2ef4de027603ba9af5ca
Date: Tue, 30 Jan 2024 23:33:48 -0800 (PST) [thread overview]
Message-ID: <65b9f7dc.170a0220.61954.1ee8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
8e5cbd3d1f6f077abdcb2ef4de027603ba9af5ca --> testing pass
Test environment and result as below:
+--------------------------+--------------------+
| Environment | dpdk_meson_compile |
+==========================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+--------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+--------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+--------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+--------------------------+--------------------+
| Debian 11 (Buster) (ARM) | 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 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27848/
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-31 7:33 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 7:33 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-31 10:08 dpdklab
2024-01-31 9:29 dpdklab
2024-01-31 8:56 dpdklab
2024-01-31 8:11 dpdklab
2024-01-31 8:09 dpdklab
2024-01-31 8:08 dpdklab
2024-01-31 8:07 dpdklab
2024-01-31 8:06 dpdklab
2024-01-31 8:04 dpdklab
2024-01-31 8:02 dpdklab
2024-01-31 8:01 dpdklab
2024-01-31 8:01 dpdklab
2024-01-31 7:59 dpdklab
2024-01-31 7:57 dpdklab
2024-01-31 7:57 dpdklab
2024-01-31 7:57 dpdklab
2024-01-31 7:52 dpdklab
2024-01-31 7:52 dpdklab
2024-01-31 7:51 dpdklab
2024-01-31 7:51 dpdklab
2024-01-31 7:48 dpdklab
2024-01-31 7:47 dpdklab
2024-01-31 7:45 dpdklab
2024-01-31 7:44 dpdklab
2024-01-31 7:44 dpdklab
2024-01-31 7:40 dpdklab
2024-01-31 7:40 dpdklab
2024-01-31 7:40 dpdklab
2024-01-31 7:40 dpdklab
2024-01-31 7:38 dpdklab
2024-01-31 7:38 dpdklab
2024-01-31 7:37 dpdklab
2024-01-31 7:36 dpdklab
2024-01-31 7:36 dpdklab
2024-01-31 7:34 dpdklab
2024-01-31 7:33 dpdklab
2024-01-31 7:33 dpdklab
2024-01-31 7:33 dpdklab
2024-01-31 7:33 dpdklab
2024-01-31 7:32 dpdklab
2024-01-31 7:31 dpdklab
2024-01-31 7:29 dpdklab
2024-01-31 7:28 dpdklab
2024-01-31 7:27 dpdklab
2024-01-31 7:26 dpdklab
2024-01-31 7:26 dpdklab
2024-01-31 7:25 dpdklab
2024-01-31 7:25 dpdklab
2024-01-31 7:25 dpdklab
2024-01-31 7:25 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=65b9f7dc.170a0220.61954.1ee8SMTPIN_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).