From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 53b2eaa21c8bc8fe2542f057f2589a26963d2891
Date: Fri, 13 Oct 2023 04:19:32 -0700 (PDT) [thread overview]
Message-ID: <652927c4.920a0220.ba260.9355SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-eventdev
53b2eaa21c8bc8fe2542f057f2589a26963d2891 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | SKIPPED | PASS |
+---------------------+--------------------+----------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
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/26462/
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-13 11:19 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 11:19 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-13 13:24 dpdklab
2023-10-13 12:46 dpdklab
2023-10-13 12:45 dpdklab
2023-10-13 12:34 dpdklab
2023-10-13 12:34 dpdklab
2023-10-13 12:16 dpdklab
2023-10-13 12:13 dpdklab
2023-10-13 12:06 dpdklab
2023-10-13 12:04 dpdklab
2023-10-13 12:01 dpdklab
2023-10-13 11:58 dpdklab
2023-10-13 11:51 dpdklab
2023-10-13 11:50 dpdklab
2023-10-13 11:50 dpdklab
2023-10-13 11:49 dpdklab
2023-10-13 11:45 dpdklab
2023-10-13 11:42 dpdklab
2023-10-13 11:39 dpdklab
2023-10-13 11:39 dpdklab
2023-10-13 11:38 dpdklab
2023-10-13 11:26 dpdklab
2023-10-13 11:26 dpdklab
2023-10-13 11:26 dpdklab
2023-10-13 11:26 dpdklab
2023-10-13 11:26 dpdklab
2023-10-13 11:25 dpdklab
2023-10-13 11:25 dpdklab
2023-10-13 11:25 dpdklab
2023-10-13 11:24 dpdklab
2023-10-13 11:23 dpdklab
2023-10-13 11:23 dpdklab
2023-10-13 11:23 dpdklab
2023-10-13 11:21 dpdklab
2023-10-13 11:20 dpdklab
2023-10-13 11:19 dpdklab
2023-10-13 11:18 dpdklab
2023-10-13 11:17 dpdklab
2023-10-13 11:17 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=652927c4.920a0220.ba260.9355SMTPIN_ADDED_MISSING@mx.google.com \
--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).