From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139438-139444 [PATCH] [v2,7/7] dma/odm: add remaining op
Date: Wed, 17 Apr 2024 04:38:20 -0700 (PDT) [thread overview]
Message-ID: <661fb4ac.050a0220.b3f0f.3e5eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240417072708.322-8-anoobj@marvell.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139444
_Testing PASS_
Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Wednesday, April 17 2024 07:27:08
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139438-139444 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian 12 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| Fedora 39 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
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
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.2.1
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29802/
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-17 11:38 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240417072708.322-8-anoobj@marvell.com>
2024-04-17 7:11 ` |SUCCESS| pw139438-139444 [PATCH v2 7/7] dma/odm: add remaining ops qemudev
2024-04-17 7:15 ` qemudev
2024-04-17 7:29 ` |WARNING| pw139444 " checkpatch
2024-04-17 8:44 ` |FAILURE| " 0-day Robot
2024-04-17 9:51 ` |SUCCESS| pw139438-139444 [PATCH] [v2,7/7] dma/odm: add remaining op dpdklab
2024-04-17 9:52 ` dpdklab
2024-04-17 9:53 ` dpdklab
2024-04-17 9:54 ` dpdklab
2024-04-17 9:55 ` dpdklab
2024-04-17 10:15 ` dpdklab
2024-04-17 10:15 ` dpdklab
2024-04-17 10:15 ` dpdklab
2024-04-17 10:16 ` dpdklab
2024-04-17 10:16 ` dpdklab
2024-04-17 10:16 ` dpdklab
2024-04-17 10:18 ` dpdklab
2024-04-17 10:18 ` dpdklab
2024-04-17 10:19 ` dpdklab
2024-04-17 10:19 ` dpdklab
2024-04-17 10:20 ` dpdklab
2024-04-17 10:20 ` dpdklab
2024-04-17 10:21 ` dpdklab
2024-04-17 10:23 ` dpdklab
2024-04-17 10:25 ` dpdklab
2024-04-17 10:26 ` dpdklab
2024-04-17 10:27 ` dpdklab
2024-04-17 10:27 ` dpdklab
2024-04-17 10:28 ` dpdklab
2024-04-17 10:39 ` dpdklab
2024-04-17 10:39 ` dpdklab
2024-04-17 10:40 ` dpdklab
2024-04-17 10:40 ` dpdklab
2024-04-17 10:40 ` dpdklab
2024-04-17 10:40 ` dpdklab
2024-04-17 10:41 ` dpdklab
2024-04-17 10:41 ` dpdklab
2024-04-17 10:42 ` dpdklab
2024-04-17 10:42 ` dpdklab
2024-04-17 10:43 ` dpdklab
2024-04-17 10:44 ` dpdklab
2024-04-17 10:44 ` dpdklab
2024-04-17 10:45 ` dpdklab
2024-04-17 10:45 ` dpdklab
2024-04-17 10:46 ` dpdklab
2024-04-17 10:46 ` dpdklab
2024-04-17 10:47 ` dpdklab
2024-04-17 10:48 ` dpdklab
2024-04-17 10:48 ` dpdklab
2024-04-17 10:51 ` dpdklab
2024-04-17 11:04 ` dpdklab
2024-04-17 11:05 ` dpdklab
2024-04-17 11:05 ` dpdklab
2024-04-17 11:06 ` dpdklab
2024-04-17 11:06 ` dpdklab
2024-04-17 11:08 ` dpdklab
2024-04-17 11:11 ` dpdklab
2024-04-17 11:12 ` dpdklab
2024-04-17 11:13 ` dpdklab
2024-04-17 11:13 ` dpdklab
2024-04-17 11:14 ` dpdklab
2024-04-17 11:14 ` dpdklab
2024-04-17 11:15 ` dpdklab
2024-04-17 11:15 ` dpdklab
2024-04-17 11:16 ` dpdklab
2024-04-17 11:17 ` dpdklab
2024-04-17 11:17 ` dpdklab
2024-04-17 11:17 ` dpdklab
2024-04-17 11:18 ` dpdklab
2024-04-17 11:18 ` dpdklab
2024-04-17 11:19 ` dpdklab
2024-04-17 11:19 ` dpdklab
2024-04-17 11:19 ` dpdklab
2024-04-17 11:20 ` dpdklab
2024-04-17 11:24 ` dpdklab
2024-04-17 11:38 ` dpdklab [this message]
2024-04-17 11:38 ` dpdklab
2024-04-17 11:39 ` dpdklab
2024-04-17 11:39 ` dpdklab
2024-04-17 11:39 ` dpdklab
2024-04-17 11:39 ` dpdklab
2024-04-17 11:39 ` dpdklab
2024-04-17 11:40 ` dpdklab
2024-04-17 11:40 ` dpdklab
2024-04-17 11:42 ` dpdklab
2024-04-17 11:43 ` dpdklab
2024-04-17 11:47 ` dpdklab
2024-04-17 11:49 ` dpdklab
2024-04-17 11:50 ` dpdklab
2024-04-17 11:54 ` dpdklab
2024-04-17 12:00 ` dpdklab
2024-04-17 12:11 ` dpdklab
2024-04-17 12:11 ` 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=661fb4ac.050a0220.b3f0f.3e5eSMTPIN_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).