From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Qi Zhang <qi.z.zhang@intel.com>
Subject: |SUCCESS| [GIT MASTER] 8e7df204672364536c04a27cef1b43d33920599b
Date: Sat, 07 Oct 2023 17:34:36 -0700 (PDT) [thread overview]
Message-ID: <6521f91c.170a0220.d035a.af56SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net-intel
8e7df204672364536c04a27cef1b43d33920599b --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Debian Buster | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 37 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
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)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
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/26383/
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-08 0:34 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 0:34 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-08 1:58 dpdklab
2023-10-08 1:39 dpdklab
2023-10-08 1:33 dpdklab
2023-10-08 1:32 dpdklab
2023-10-08 1:31 dpdklab
2023-10-08 1:28 dpdklab
2023-10-08 1:26 dpdklab
2023-10-08 1:22 dpdklab
2023-10-08 1:17 dpdklab
2023-10-08 1:15 dpdklab
2023-10-08 1:13 dpdklab
2023-10-08 1:13 dpdklab
2023-10-08 1:11 dpdklab
2023-10-08 1:11 dpdklab
2023-10-08 1:06 dpdklab
2023-10-08 0:58 dpdklab
2023-10-08 0:42 dpdklab
2023-10-08 0:40 dpdklab
2023-10-08 0:32 dpdklab
2023-10-08 0:21 dpdklab
2023-10-08 0:13 dpdklab
2023-10-08 0:12 dpdklab
2023-10-08 0:06 dpdklab
2023-10-08 0:05 dpdklab
2023-10-07 23:54 dpdklab
2023-10-07 23:53 dpdklab
2023-10-07 23:52 dpdklab
2023-10-07 23:52 dpdklab
2023-10-07 23:51 dpdklab
2023-10-07 23:51 dpdklab
2023-10-07 23:50 dpdklab
2023-10-07 23:49 dpdklab
2023-10-07 23:49 dpdklab
2023-10-07 23:48 dpdklab
2023-10-07 23:47 dpdklab
2023-10-07 23:47 dpdklab
2023-10-07 23:45 dpdklab
2023-10-07 23:43 dpdklab
2023-10-07 23:42 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=6521f91c.170a0220.d035a.af56SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=qi.z.zhang@intel.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).