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] e4bd9e583aa3a82562e39748f450930be2a5fbbb
Date: Fri, 02 Feb 2024 09:49:37 -0800 (PST) [thread overview]
Message-ID: <65bd2b31.250a0220.1ccd3.372bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-eventdev
e4bd9e583aa3a82562e39748f450930be2a5fbbb --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Buster | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27891/
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-02 17:49 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 17:49 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-02 22:59 dpdklab
2024-02-02 22:24 dpdklab
2024-02-02 19:40 dpdklab
2024-02-02 19:17 dpdklab
2024-02-02 18:42 dpdklab
2024-02-02 18:35 dpdklab
2024-02-02 18:33 dpdklab
2024-02-02 18:32 dpdklab
2024-02-02 18:32 dpdklab
2024-02-02 18:32 dpdklab
2024-02-02 18:31 dpdklab
2024-02-02 18:30 dpdklab
2024-02-02 18:29 dpdklab
2024-02-02 18:17 dpdklab
2024-02-02 18:12 dpdklab
2024-02-02 18:12 dpdklab
2024-02-02 18:10 dpdklab
2024-02-02 18:10 dpdklab
2024-02-02 18:10 dpdklab
2024-02-02 18:05 dpdklab
2024-02-02 18:03 dpdklab
2024-02-02 18:03 dpdklab
2024-02-02 18:03 dpdklab
2024-02-02 18:01 dpdklab
2024-02-02 18:01 dpdklab
2024-02-02 18:00 dpdklab
2024-02-02 18:00 dpdklab
2024-02-02 18:00 dpdklab
2024-02-02 17:59 dpdklab
2024-02-02 17:59 dpdklab
2024-02-02 17:59 dpdklab
2024-02-02 17:57 dpdklab
2024-02-02 17:56 dpdklab
2024-02-02 17:56 dpdklab
2024-02-02 17:55 dpdklab
2024-02-02 17:55 dpdklab
2024-02-02 17:54 dpdklab
2024-02-02 17:53 dpdklab
2024-02-02 17:53 dpdklab
2024-02-02 17:53 dpdklab
2024-02-02 17:52 dpdklab
2024-02-02 17:52 dpdklab
2024-02-02 17:51 dpdklab
2024-02-02 17:51 dpdklab
2024-02-02 17:50 dpdklab
2024-02-02 17:50 dpdklab
2024-02-02 17:50 dpdklab
2024-02-02 17:50 dpdklab
2024-02-02 17:49 dpdklab
2024-02-02 17:49 dpdklab
2024-02-02 17:49 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=65bd2b31.250a0220.1ccd3.372bSMTPIN_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).