From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135295-135301 [PATCH] [v4,7/7] dts: add scatter test sui
Date: Mon, 18 Dec 2023 14:19:01 -0800 (PST) [thread overview]
Message-ID: <6580c555.050a0220.b6fa9.e0b6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135301
_Testing PASS_
Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Monday, December 18 2023 18:12:21
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
135295-135301 --> testing pass
Test environment and result as below:
+--------------------------+--------------------+
| Environment | dpdk_meson_compile |
+==========================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+--------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+--------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+--------------------------+--------------------+
| Fedora 38 (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 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.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/28674/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-18 22:19 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 22:19 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-19 1:02 dpdklab
2023-12-19 0:08 dpdklab
2023-12-18 23:26 dpdklab
2023-12-18 23:11 dpdklab
2023-12-18 23:04 dpdklab
2023-12-18 22:56 dpdklab
2023-12-18 22:56 dpdklab
2023-12-18 22:51 dpdklab
2023-12-18 22:48 dpdklab
2023-12-18 22:47 dpdklab
2023-12-18 22:46 dpdklab
2023-12-18 22:45 dpdklab
2023-12-18 22:44 dpdklab
2023-12-18 22:43 dpdklab
2023-12-18 22:43 dpdklab
2023-12-18 22:42 dpdklab
2023-12-18 22:42 dpdklab
2023-12-18 22:42 dpdklab
2023-12-18 22:42 dpdklab
2023-12-18 22:41 dpdklab
2023-12-18 22:40 dpdklab
2023-12-18 22:40 dpdklab
2023-12-18 22:40 dpdklab
2023-12-18 22:38 dpdklab
2023-12-18 22:38 dpdklab
2023-12-18 22:38 dpdklab
2023-12-18 22:37 dpdklab
2023-12-18 22:36 dpdklab
2023-12-18 22:35 dpdklab
2023-12-18 22:35 dpdklab
2023-12-18 22:35 dpdklab
2023-12-18 22:34 dpdklab
2023-12-18 22:33 dpdklab
2023-12-18 22:32 dpdklab
2023-12-18 22:31 dpdklab
2023-12-18 22:30 dpdklab
2023-12-18 22:30 dpdklab
2023-12-18 22:30 dpdklab
2023-12-18 22:29 dpdklab
2023-12-18 22:28 dpdklab
2023-12-18 22:26 dpdklab
2023-12-18 22:25 dpdklab
2023-12-18 22:20 dpdklab
2023-12-18 22:18 dpdklab
2023-12-18 22:14 dpdklab
2023-12-18 22:14 dpdklab
2023-12-18 22:13 dpdklab
2023-12-18 22:12 dpdklab
2023-12-18 22:10 dpdklab
2023-12-18 22:10 dpdklab
2023-12-18 22:09 dpdklab
2023-12-18 22:09 dpdklab
2023-12-18 22:09 dpdklab
2023-12-18 22:09 dpdklab
2023-12-18 22:08 dpdklab
2023-12-18 22:08 dpdklab
2023-12-18 22:08 dpdklab
2023-12-18 22:07 dpdklab
2023-12-18 22:04 dpdklab
2023-12-18 22:03 dpdklab
2023-12-18 22:03 dpdklab
2023-12-18 22:02 dpdklab
2023-12-18 22:02 dpdklab
2023-12-18 22:01 dpdklab
2023-12-18 22:01 dpdklab
2023-12-18 21:59 dpdklab
2023-12-18 21:58 dpdklab
2023-12-18 21:51 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=6580c555.050a0220.b6fa9.e0b6SMTPIN_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).