From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| pw133341-133365 [PATCH] [v3,25/25] doc: add a entry in the
Date: Thu, 26 Oct 2023 00:51:11 -0700 (PDT) [thread overview]
Message-ID: <653a1a6f.4a0a0220.25c98.21a2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133365
_Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Thursday, October 26 2023 06:43:24
DPDK git baseline: Repo:dpdk-next-net
Branch: master
CommitID:02384bb8ec7d9cb9da4271d18a0b50e8bb413f4f
133341-133365 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 37 | 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)
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28079/
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-26 7:51 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 7:51 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-28 0:35 dpdklab
2023-10-26 20:30 dpdklab
2023-10-26 20:21 dpdklab
2023-10-26 19:29 dpdklab
2023-10-26 19:21 dpdklab
2023-10-26 8:58 dpdklab
2023-10-26 8:50 dpdklab
2023-10-26 8:48 dpdklab
2023-10-26 8:45 dpdklab
2023-10-26 8:41 dpdklab
2023-10-26 8:39 dpdklab
2023-10-26 8:38 dpdklab
2023-10-26 8:36 dpdklab
2023-10-26 8:33 dpdklab
2023-10-26 8:30 dpdklab
2023-10-26 8:26 dpdklab
2023-10-26 8:24 dpdklab
2023-10-26 8:16 dpdklab
2023-10-26 8:14 dpdklab
2023-10-26 8:13 dpdklab
2023-10-26 8:12 dpdklab
2023-10-26 8:10 dpdklab
2023-10-26 8:07 dpdklab
2023-10-26 8:07 dpdklab
2023-10-26 8:05 dpdklab
2023-10-26 8:05 dpdklab
2023-10-26 8:05 dpdklab
2023-10-26 8:04 dpdklab
2023-10-26 8:03 dpdklab
2023-10-26 7:59 dpdklab
2023-10-26 7:59 dpdklab
2023-10-26 7:53 dpdklab
2023-10-26 7:52 dpdklab
2023-10-26 7:51 dpdklab
2023-10-26 7:51 dpdklab
2023-10-26 7:50 dpdklab
2023-10-26 7:50 dpdklab
2023-10-26 7:50 dpdklab
2023-10-26 7:50 dpdklab
2023-10-26 7:50 dpdklab
2023-10-26 7:49 dpdklab
2023-10-26 7:49 dpdklab
2023-10-26 7:49 dpdklab
2023-10-26 7:49 dpdklab
2023-10-26 7:48 dpdklab
2023-10-26 7:48 dpdklab
2023-10-26 7:47 dpdklab
2023-10-26 7:46 dpdklab
2023-10-26 7:46 dpdklab
2023-10-26 7:45 dpdklab
2023-10-26 7:45 dpdklab
2023-10-26 7:44 dpdklab
2023-10-26 7:43 dpdklab
2023-10-26 7:42 dpdklab
2023-10-26 7:41 dpdklab
2023-10-26 7:40 dpdklab
2023-10-26 7:39 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=653a1a6f.4a0a0220.25c98.21a2SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@amd.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).