From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135714-135720 [PATCH] [v6,7/7] dts: add pmd_buffer_scatt
Date: Thu, 04 Jan 2024 01:28:44 -0800 (PST) [thread overview]
Message-ID: <65967a4c.170a0220.1b37d.59b8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135720
_Testing PASS_
Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Wednesday, January 03 2024 22:32:06
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871
135714-135720 --> testing pass
Test environment and result as below:
+--------------------------+--------------------+
| Environment | dpdk_meson_compile |
+==========================+====================+
| Debian 11 (Buster) (ARM) | PASS |
+--------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+--------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+--------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+--------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+--------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+--------------------------+--------------------+
| Fedora 38 (ARM Clang) | PASS |
+--------------------------+--------------------+
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Fedora 38 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 16.0.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28783/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-04 9:28 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 9:28 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-05 0:49 dpdklab
2024-01-05 0:43 dpdklab
2024-01-04 20:36 dpdklab
2024-01-04 10:22 dpdklab
2024-01-04 10:19 dpdklab
2024-01-04 10:18 dpdklab
2024-01-04 10:07 dpdklab
2024-01-04 10:05 dpdklab
2024-01-04 10:04 dpdklab
2024-01-04 10:04 dpdklab
2024-01-04 10:04 dpdklab
2024-01-04 10:01 dpdklab
2024-01-04 10:01 dpdklab
2024-01-04 10:01 dpdklab
2024-01-04 9:59 dpdklab
2024-01-04 9:58 dpdklab
2024-01-04 9:41 dpdklab
2024-01-04 9:23 dpdklab
2024-01-04 9:20 dpdklab
2024-01-04 9:19 dpdklab
2024-01-04 9:16 dpdklab
2024-01-04 9:16 dpdklab
2024-01-04 9:12 dpdklab
2024-01-04 9:08 dpdklab
2024-01-04 9:07 dpdklab
2024-01-04 9:05 dpdklab
2024-01-04 8:56 dpdklab
2024-01-04 8:27 dpdklab
2024-01-04 8:25 dpdklab
2024-01-04 8:19 dpdklab
2024-01-04 8:17 dpdklab
2024-01-04 8:09 dpdklab
2024-01-04 8:04 dpdklab
2024-01-04 8:02 dpdklab
2024-01-04 7:58 dpdklab
2024-01-04 7:56 dpdklab
2024-01-04 7:46 dpdklab
2024-01-04 7:36 dpdklab
2024-01-04 7:11 dpdklab
2024-01-04 7:10 dpdklab
2024-01-04 7:09 dpdklab
2024-01-04 7:07 dpdklab
2024-01-04 7:07 dpdklab
2024-01-04 7:06 dpdklab
2024-01-04 7:06 dpdklab
2024-01-04 7:06 dpdklab
2024-01-04 7:06 dpdklab
2024-01-04 7:05 dpdklab
2024-01-04 7:04 dpdklab
2024-01-04 4:56 dpdklab
2024-01-04 4:42 dpdklab
2024-01-04 4:23 dpdklab
2024-01-04 3:56 dpdklab
2024-01-04 3:44 dpdklab
2024-01-04 3:39 dpdklab
2024-01-04 3:38 dpdklab
2024-01-04 3:38 dpdklab
2024-01-04 3:37 dpdklab
2024-01-04 3:33 dpdklab
2024-01-04 3:33 dpdklab
2024-01-04 3:33 dpdklab
2024-01-04 3:33 dpdklab
2024-01-04 3:33 dpdklab
2024-01-04 3:31 dpdklab
2024-01-04 3:31 dpdklab
2024-01-04 3:30 dpdklab
2024-01-04 3:30 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=65967a4c.170a0220.1b37d.59b8SMTPIN_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).