From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Jerin Jacob <jerinj@marvell.com>
Subject: |SUCCESS| [GIT MASTER] 79d638d4cfc0eddaeaf61f5f41043811806e8b4d
Date: Thu, 29 Feb 2024 16:45:26 -0800 (PST) [thread overview]
Message-ID: <65e12526.620a0220.cc8da.9a5aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-eventdev
79d638d4cfc0eddaeaf61f5f41043811806e8b4d --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (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)
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.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/28239/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-03-01 0:45 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 0:45 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-03 20:28 dpdklab
2024-03-03 19:55 dpdklab
2024-03-02 11:12 dpdklab
2024-03-01 10:58 dpdklab
2024-03-01 10:53 dpdklab
2024-03-01 10:48 dpdklab
2024-03-01 7:21 dpdklab
2024-03-01 3:21 dpdklab
2024-03-01 3:04 dpdklab
2024-03-01 2:14 dpdklab
2024-03-01 2:09 dpdklab
2024-03-01 1:58 dpdklab
2024-03-01 1:35 dpdklab
2024-03-01 1:34 dpdklab
2024-03-01 1:33 dpdklab
2024-03-01 1:09 dpdklab
2024-03-01 1:07 dpdklab
2024-03-01 1:06 dpdklab
2024-03-01 1:00 dpdklab
2024-03-01 0:58 dpdklab
2024-03-01 0:50 dpdklab
2024-03-01 0:49 dpdklab
2024-03-01 0:49 dpdklab
2024-03-01 0:47 dpdklab
2024-03-01 0:47 dpdklab
2024-03-01 0:46 dpdklab
2024-03-01 0:45 dpdklab
2024-03-01 0:45 dpdklab
2024-03-01 0:45 dpdklab
2024-03-01 0:41 dpdklab
2024-03-01 0:41 dpdklab
2024-03-01 0:40 dpdklab
2024-03-01 0:40 dpdklab
2024-03-01 0:40 dpdklab
2024-03-01 0:39 dpdklab
2024-03-01 0:39 dpdklab
2024-03-01 0:37 dpdklab
2024-03-01 0:37 dpdklab
2024-03-01 0:36 dpdklab
2024-03-01 0:36 dpdklab
2024-03-01 0:35 dpdklab
2024-03-01 0:35 dpdklab
2024-03-01 0:35 dpdklab
2024-03-01 0:34 dpdklab
2024-03-01 0:34 dpdklab
2024-03-01 0:34 dpdklab
2024-03-01 0:33 dpdklab
2024-03-01 0:32 dpdklab
2024-03-01 0:25 dpdklab
2024-03-01 0:24 dpdklab
2024-03-01 0:15 dpdklab
2024-02-29 20:45 dpdklab
2024-02-29 20:41 dpdklab
2024-02-29 20:34 dpdklab
2024-02-29 20:22 dpdklab
2024-02-29 20:22 dpdklab
2024-02-29 20:10 dpdklab
2024-02-29 20:04 dpdklab
2024-02-29 19: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=65e12526.620a0220.cc8da.9a5aSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=jerinj@marvell.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).