From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132204-132215 [PATCH] [v8,12/12] app/test: add event DMA
Date: Fri, 29 Sep 2023 08:28:28 -0700 (PDT) [thread overview]
Message-ID: <6516ed1c.050a0220.398ad.cc1fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132215
_Testing PASS_
Submitter: Amit Prakash Shukla <amitprakashs@marvell.com>
Date: Friday, September 29 2023 11:50:51
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: master
CommitID:fba04ad5c3ae054f8703d82446911a03aee31a87
132204-132215 --> testing pass
Test environment and result as below:
+--------------------------+--------------------+
| Environment | dpdk_meson_compile |
+==========================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+--------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+--------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+--------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+--------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+--------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+--------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27787/
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-29 15:28 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 15:28 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-29 16:44 dpdklab
2023-09-29 16:35 dpdklab
2023-09-29 16:32 dpdklab
2023-09-29 16:14 dpdklab
2023-09-29 16:14 dpdklab
2023-09-29 16:11 dpdklab
2023-09-29 16:11 dpdklab
2023-09-29 16:05 dpdklab
2023-09-29 16:03 dpdklab
2023-09-29 16:03 dpdklab
2023-09-29 16:02 dpdklab
2023-09-29 16:02 dpdklab
2023-09-29 16:00 dpdklab
2023-09-29 15:52 dpdklab
2023-09-29 15:52 dpdklab
2023-09-29 15:51 dpdklab
2023-09-29 15:50 dpdklab
2023-09-29 15:49 dpdklab
2023-09-29 15:48 dpdklab
2023-09-29 15:48 dpdklab
2023-09-29 15:45 dpdklab
2023-09-29 15:41 dpdklab
2023-09-29 15:40 dpdklab
2023-09-29 15:38 dpdklab
2023-09-29 15:35 dpdklab
2023-09-29 15:35 dpdklab
2023-09-29 15:35 dpdklab
2023-09-29 15:35 dpdklab
2023-09-29 15:33 dpdklab
2023-09-29 15:28 dpdklab
2023-09-29 15:28 dpdklab
2023-09-29 15:28 dpdklab
2023-09-29 15:22 dpdklab
2023-09-29 15:22 dpdklab
2023-09-29 15:22 dpdklab
2023-09-29 15:22 dpdklab
2023-09-29 15:22 dpdklab
2023-09-29 15:17 dpdklab
2023-09-29 15:17 dpdklab
2023-09-29 15:17 dpdklab
2023-09-29 15:16 dpdklab
2023-09-29 15:16 dpdklab
2023-09-29 15:16 dpdklab
2023-09-29 15:12 dpdklab
2023-09-29 15:11 dpdklab
2023-09-29 15:10 dpdklab
2023-09-29 15:01 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=6516ed1c.050a0220.398ad.cc1fSMTPIN_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).