From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136171-136177 [PATCH] [v3,8/8] examples/dma: replace get
Date: Thu, 25 Jan 2024 23:58:01 -0800 (PST) [thread overview]
Message-ID: <65b36609.050a0220.7d49d.1f78SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136177
_Testing PASS_
Submitter: fengchengwen <fengchengwen@huawei.com>
Date: Friday, January 26 2024 06:10:13
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2ecc673e5e9a19850ba76d6a976596890f2dade1
136171-136177 --> testing pass
Test environment and result as below:
+----------------------+--------------------+
| Environment | dpdk_meson_compile |
+======================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+----------------------+--------------------+
| Fedora 37 (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)
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28970/
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-26 7:58 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 7:58 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-26 11:05 dpdklab
2024-01-26 10:44 dpdklab
2024-01-26 10:12 dpdklab
2024-01-26 10:11 dpdklab
2024-01-26 10:10 dpdklab
2024-01-26 10:08 dpdklab
2024-01-26 10:07 dpdklab
2024-01-26 10:06 dpdklab
2024-01-26 10:06 dpdklab
2024-01-26 10:05 dpdklab
2024-01-26 9:56 dpdklab
2024-01-26 9:41 dpdklab
2024-01-26 9:39 dpdklab
2024-01-26 9:39 dpdklab
2024-01-26 9:38 dpdklab
2024-01-26 9:28 dpdklab
2024-01-26 9:27 dpdklab
2024-01-26 9:20 dpdklab
2024-01-26 9:17 dpdklab
2024-01-26 9:15 dpdklab
2024-01-26 9:15 dpdklab
2024-01-26 9:13 dpdklab
2024-01-26 9:13 dpdklab
2024-01-26 9:12 dpdklab
2024-01-26 9:11 dpdklab
2024-01-26 9:06 dpdklab
2024-01-26 9:05 dpdklab
2024-01-26 9:02 dpdklab
2024-01-26 8:56 dpdklab
2024-01-26 8:54 dpdklab
2024-01-26 8:52 dpdklab
2024-01-26 8:47 dpdklab
2024-01-26 8:46 dpdklab
2024-01-26 8:44 dpdklab
2024-01-26 8:42 dpdklab
2024-01-26 8:42 dpdklab
2024-01-26 8:37 dpdklab
2024-01-26 8:33 dpdklab
2024-01-26 8:29 dpdklab
2024-01-26 8:25 dpdklab
2024-01-26 8:22 dpdklab
2024-01-26 8:19 dpdklab
2024-01-26 8:18 dpdklab
2024-01-26 8:18 dpdklab
2024-01-26 8:18 dpdklab
2024-01-26 8:12 dpdklab
2024-01-26 8:11 dpdklab
2024-01-26 8:08 dpdklab
2024-01-26 8:05 dpdklab
2024-01-26 8:05 dpdklab
2024-01-26 8:04 dpdklab
2024-01-26 8:04 dpdklab
2024-01-26 8:04 dpdklab
2024-01-26 8:03 dpdklab
2024-01-26 8:03 dpdklab
2024-01-26 8:03 dpdklab
2024-01-26 8:02 dpdklab
2024-01-26 8:02 dpdklab
2024-01-26 8:01 dpdklab
2024-01-26 8:01 dpdklab
2024-01-26 8:01 dpdklab
2024-01-26 8:01 dpdklab
2024-01-26 8:00 dpdklab
2024-01-26 8:00 dpdklab
2024-01-26 7:59 dpdklab
2024-01-26 7:59 dpdklab
2024-01-26 7:59 dpdklab
2024-01-26 7:57 dpdklab
2024-01-26 7:56 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=65b36609.050a0220.7d49d.1f78SMTPIN_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).