From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135218 [PATCH] maintainers: add new maintainer to DMA pe
Date: Thu, 14 Dec 2023 17:52:18 -0800 (PST) [thread overview]
Message-ID: <657bb152.170a0220.2f818.c485SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135218
_Testing PASS_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Friday, December 15 2023 00:35:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
135218 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Fedora 37 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.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)
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 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28640/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-15 1:52 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 1:52 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-15 12:03 dpdklab
2023-12-15 3:33 dpdklab
2023-12-15 3:15 dpdklab
2023-12-15 3:05 dpdklab
2023-12-15 2:19 dpdklab
2023-12-15 2:19 dpdklab
2023-12-15 2:12 dpdklab
2023-12-15 2:11 dpdklab
2023-12-15 2:06 dpdklab
2023-12-15 2:03 dpdklab
2023-12-15 1:59 dpdklab
2023-12-15 1:59 dpdklab
2023-12-15 1:58 dpdklab
2023-12-15 1:54 dpdklab
2023-12-15 1:50 dpdklab
2023-12-15 1:50 dpdklab
2023-12-15 1:50 dpdklab
2023-12-15 1:50 dpdklab
2023-12-15 1:50 dpdklab
2023-12-15 1:49 dpdklab
2023-12-15 1:49 dpdklab
2023-12-15 1:46 dpdklab
2023-12-15 1:46 dpdklab
2023-12-15 1:46 dpdklab
2023-12-15 1:46 dpdklab
2023-12-15 1:46 dpdklab
2023-12-15 1:45 dpdklab
2023-12-15 1:44 dpdklab
2023-12-15 1:44 dpdklab
2023-12-15 1:44 dpdklab
2023-12-15 1:43 dpdklab
2023-12-15 1:43 dpdklab
2023-12-15 1:43 dpdklab
2023-12-15 1:43 dpdklab
2023-12-15 1:43 dpdklab
2023-12-15 1:42 dpdklab
2023-12-15 1:42 dpdklab
2023-12-15 1:37 dpdklab
2023-12-15 1:37 dpdklab
2023-12-15 1:36 dpdklab
2023-12-15 1:36 dpdklab
2023-12-15 1:36 dpdklab
2023-12-15 1:36 dpdklab
2023-12-15 1:36 dpdklab
2023-12-15 1:36 dpdklab
2023-12-15 1:35 dpdklab
2023-12-15 1:35 dpdklab
2023-12-15 1:35 dpdklab
2023-12-15 1:35 dpdklab
2023-12-15 1:35 dpdklab
2023-12-15 1:35 dpdklab
2023-12-15 1:35 dpdklab
2023-12-15 1:34 dpdklab
2023-12-15 1:34 dpdklab
2023-12-15 1:34 dpdklab
2023-12-15 1:33 dpdklab
2023-12-15 1:31 dpdklab
2023-12-15 1:28 dpdklab
2023-12-15 1:27 dpdklab
2023-12-15 1:27 dpdklab
2023-12-15 1:27 dpdklab
2023-12-15 1:26 dpdklab
2023-12-15 1:26 dpdklab
2023-12-15 1:26 dpdklab
2023-12-15 1:25 dpdklab
2023-12-15 1:25 dpdklab
2023-12-15 1:25 dpdklab
2023-12-15 1:24 dpdklab
2023-12-15 1:24 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=657bb152.170a0220.2f818.c485SMTPIN_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).