From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw131939-131950 [PATCH] [v4,12/12] app/test: add event DMA
Date: Tue, 26 Sep 2023 13:54:42 -0700 (PDT) [thread overview]
Message-ID: <65134512.170a0220.87b3a.7996SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/131950
_Testing PASS_
Submitter: Amit Prakash Shukla <amitprakashs@marvell.com>
Date: Tuesday, September 26 2023 10:32:33
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: master
CommitID:53b3521fa4b21174a4e620e8009ffc65396226e2
131939-131950 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
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/27728/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-26 20:54 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 20:54 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-27 2:29 dpdklab
2023-09-26 21:21 dpdklab
2023-09-26 21:16 dpdklab
2023-09-26 21:10 dpdklab
2023-09-26 21:10 dpdklab
2023-09-26 20:52 dpdklab
2023-09-26 20:46 dpdklab
2023-09-26 20:44 dpdklab
2023-09-26 20:35 dpdklab
2023-09-26 20:35 dpdklab
2023-09-26 20:31 dpdklab
2023-09-26 20:30 dpdklab
2023-09-26 20:28 dpdklab
2023-09-26 20:21 dpdklab
2023-09-26 20:19 dpdklab
2023-09-26 20:16 dpdklab
2023-09-26 20:14 dpdklab
2023-09-26 20:14 dpdklab
2023-09-26 20:12 dpdklab
2023-09-26 20:00 dpdklab
2023-09-26 19:58 dpdklab
2023-09-26 19:56 dpdklab
2023-09-26 19:54 dpdklab
2023-09-26 19:50 dpdklab
2023-09-26 19:49 dpdklab
2023-09-26 19:48 dpdklab
2023-09-26 19:47 dpdklab
2023-09-26 19:39 dpdklab
2023-09-26 19:37 dpdklab
2023-09-26 19:35 dpdklab
2023-09-26 19:25 dpdklab
2023-09-26 19:19 dpdklab
2023-09-26 19:16 dpdklab
2023-09-26 19:15 dpdklab
2023-09-26 19:15 dpdklab
2023-09-26 19:14 dpdklab
2023-09-26 19:05 dpdklab
2023-09-26 18:59 dpdklab
2023-09-26 18:58 dpdklab
2023-09-26 18:50 dpdklab
2023-09-26 18:43 dpdklab
2023-09-26 18:42 dpdklab
2023-09-26 18:41 dpdklab
2023-09-26 18:40 dpdklab
2023-09-26 18:38 dpdklab
2023-09-26 18:34 dpdklab
2023-09-26 18:32 dpdklab
2023-09-26 18:31 dpdklab
2023-09-26 18:04 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=65134512.170a0220.87b3a.7996SMTPIN_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).