From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] ca88db3ae76d878a8febe3fe1effe0b677403845
Date: Tue, 28 Feb 2023 13:32:39 +0000 (UTC) [thread overview]
Message-ID: <20230228133239.806DF601B1@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
_Testing PASS_
Branch: dpdk-next-eventdev
ca88db3ae76d878a8febe3fe1effe0b677403845 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+----------------------+----------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_unit_test |
+========================================+====================+======================+================+
| FreeBSD 13 | PASS | SKIPPED | SKIPPED |
+----------------------------------------+--------------------+----------------------+----------------+
| Windows Server 2019 | PASS | PASS | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS | SKIPPED | SKIPPED |
+----------------------------------------+--------------------+----------------------+----------------+
| CentOS Stream 8 | SKIPPED | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| RHEL8 | SKIPPED | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| Debian Buster | SKIPPED | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| openSUSE Leap 15 | SKIPPED | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/23521/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-28 13:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 13:32 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-28 14:35 dpdklab
2023-02-28 14:33 dpdklab
2023-02-28 14:32 dpdklab
2023-02-28 13:58 dpdklab
2023-02-28 13:50 dpdklab
2023-02-28 13:42 dpdklab
2023-02-28 13:40 dpdklab
2023-02-28 13:39 dpdklab
2023-02-28 13:37 dpdklab
2023-02-28 13:36 dpdklab
2023-02-28 13:29 dpdklab
2023-02-28 13:25 dpdklab
2023-02-28 13:11 dpdklab
2023-02-28 12:39 dpdklab
2023-02-28 12:35 dpdklab
2023-02-28 12:27 dpdklab
2023-02-28 12:26 dpdklab
2023-02-28 12:26 dpdklab
2023-02-28 12:20 dpdklab
2023-02-28 12:19 dpdklab
2023-02-28 12:19 dpdklab
2023-02-28 12:15 dpdklab
2023-02-28 12:11 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=20230228133239.806DF601B1@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).