From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139178-139179 [PATCH] [2/2] dma/cnxk: remove completion
Date: Sat, 06 Apr 2024 04:42:49 -0700 (PDT) [thread overview]
Message-ID: <66113539.050a0220.bee1a.a81eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240406101311.11044-2-pbhagavatula@marvell.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139179
_Testing PASS_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Saturday, April 06 2024 10:13:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139178-139179 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian 12 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Fedora 39 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29733/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-04-06 11:42 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240406101311.11044-2-pbhagavatula@marvell.com>
2024-04-06 9:50 ` |SUCCESS| pw139178-139179 [PATCH 2/2] dma/cnxk: remove completion pool qemudev
2024-04-06 9:55 ` qemudev
2024-04-06 10:15 ` |SUCCESS| pw139179 " checkpatch
2024-04-06 11:03 ` |FAILURE| " 0-day Robot
2024-04-06 11:07 ` |SUCCESS| pw139178-139179 [PATCH] [2/2] dma/cnxk: remove completion dpdklab
2024-04-06 11:07 ` dpdklab
2024-04-06 11:08 ` dpdklab
2024-04-06 11:08 ` dpdklab
2024-04-06 11:13 ` dpdklab
2024-04-06 11:13 ` dpdklab
2024-04-06 11:13 ` |FAILURE| " dpdklab
2024-04-06 11:13 ` |SUCCESS| " dpdklab
2024-04-06 11:14 ` dpdklab
2024-04-06 11:14 ` dpdklab
2024-04-06 11:14 ` dpdklab
2024-04-06 11:15 ` dpdklab
2024-04-06 11:15 ` dpdklab
2024-04-06 11:15 ` dpdklab
2024-04-06 11:16 ` dpdklab
2024-04-06 11:16 ` dpdklab
2024-04-06 11:17 ` dpdklab
2024-04-06 11:17 ` dpdklab
2024-04-06 11:17 ` dpdklab
2024-04-06 11:17 ` dpdklab
2024-04-06 11:18 ` |FAILURE| " dpdklab
2024-04-06 11:18 ` |SUCCESS| " dpdklab
2024-04-06 11:18 ` |FAILURE| " dpdklab
2024-04-06 11:18 ` |SUCCESS| " dpdklab
2024-04-06 11:18 ` dpdklab
2024-04-06 11:19 ` |FAILURE| " dpdklab
2024-04-06 11:19 ` |SUCCESS| " dpdklab
2024-04-06 11:19 ` |FAILURE| " dpdklab
2024-04-06 11:19 ` |SUCCESS| " dpdklab
2024-04-06 11:20 ` |FAILURE| " dpdklab
2024-04-06 11:20 ` dpdklab
2024-04-06 11:20 ` |SUCCESS| " dpdklab
2024-04-06 11:20 ` |FAILURE| " dpdklab
2024-04-06 11:20 ` dpdklab
2024-04-06 11:20 ` |SUCCESS| " dpdklab
2024-04-06 11:20 ` dpdklab
2024-04-06 11:22 ` dpdklab
2024-04-06 11:23 ` dpdklab
2024-04-06 11:24 ` dpdklab
2024-04-06 11:24 ` dpdklab
2024-04-06 11:24 ` dpdklab
2024-04-06 11:24 ` |FAILURE| " dpdklab
2024-04-06 11:25 ` |SUCCESS| " dpdklab
2024-04-06 11:25 ` dpdklab
2024-04-06 11:25 ` dpdklab
2024-04-06 11:25 ` dpdklab
2024-04-06 11:30 ` dpdklab
2024-04-06 11:31 ` dpdklab
2024-04-06 11:32 ` dpdklab
2024-04-06 11:33 ` dpdklab
2024-04-06 11:34 ` dpdklab
2024-04-06 11:34 ` dpdklab
2024-04-06 11:34 ` dpdklab
2024-04-06 11:34 ` dpdklab
2024-04-06 11:34 ` dpdklab
2024-04-06 11:34 ` dpdklab
2024-04-06 11:35 ` dpdklab
2024-04-06 11:35 ` dpdklab
2024-04-06 11:36 ` dpdklab
2024-04-06 11:37 ` dpdklab
2024-04-06 11:37 ` |FAILURE| " dpdklab
2024-04-06 11:38 ` |SUCCESS| " dpdklab
2024-04-06 11:38 ` dpdklab
2024-04-06 11:39 ` dpdklab
2024-04-06 11:39 ` dpdklab
2024-04-06 11:39 ` dpdklab
2024-04-06 11:39 ` dpdklab
2024-04-06 11:40 ` dpdklab
2024-04-06 11:42 ` dpdklab
2024-04-06 11:42 ` dpdklab
2024-04-06 11:42 ` dpdklab
2024-04-06 11:42 ` dpdklab
2024-04-06 11:42 ` dpdklab [this message]
2024-04-06 11:43 ` dpdklab
2024-04-06 11:43 ` dpdklab
2024-04-06 11:45 ` dpdklab
2024-04-06 11:58 ` dpdklab
2024-04-06 12:00 ` dpdklab
2024-04-06 12:04 ` |FAILURE| " dpdklab
2024-04-06 12:05 ` |SUCCESS| " dpdklab
2024-04-06 12:13 ` dpdklab
2024-04-06 12:20 ` dpdklab
2024-04-06 12:44 ` |FAILURE| " dpdklab
2024-04-06 12:50 ` 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=66113539.050a0220.bee1a.a81eSMTPIN_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).