From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133066 [PATCH] maintainers: update email address
Date: Fri, 20 Oct 2023 02:44:34 -0700 (PDT) [thread overview]
Message-ID: <65324c02.920a0220.eb16.4a9fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133066
_Testing PASS_
Submitter: Chenbo Xia <chenbox@nvidia.com>
Date: Friday, October 20 2023 08:51:30
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2cd2cf0cc53a508c4bd951a980ec534a646260de
133066 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | 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 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
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28017/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-20 9:44 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 9:44 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-20 10:51 dpdklab
2023-10-20 10:21 dpdklab
2023-10-20 10:14 dpdklab
2023-10-20 10:14 dpdklab
2023-10-20 10:14 dpdklab
2023-10-20 10:10 dpdklab
2023-10-20 10:10 dpdklab
2023-10-20 10:10 dpdklab
2023-10-20 10:10 dpdklab
2023-10-20 10:07 dpdklab
2023-10-20 10:07 dpdklab
2023-10-20 10:07 dpdklab
2023-10-20 10:06 dpdklab
2023-10-20 10:05 dpdklab
2023-10-20 10:04 dpdklab
[not found] <20231020085130.42945-1-chenbox@nvidia.com>
2023-10-20 8:36 ` qemudev
2023-10-20 8:41 ` qemudev
2023-10-20 8:52 ` checkpatch
2023-10-20 9:59 ` 0-day Robot
2023-10-20 9:56 dpdklab
2023-10-20 9:51 dpdklab
2023-10-20 9:48 dpdklab
2023-10-20 9:48 dpdklab
2023-10-20 9:47 dpdklab
2023-10-20 9:47 dpdklab
2023-10-20 9:46 dpdklab
2023-10-20 9:46 dpdklab
2023-10-20 9:46 dpdklab
2023-10-20 9:45 dpdklab
2023-10-20 9:45 dpdklab
2023-10-20 9:44 dpdklab
2023-10-20 9:44 dpdklab
2023-10-20 9:44 dpdklab
2023-10-20 9:44 dpdklab
2023-10-20 9:44 dpdklab
2023-10-20 9:42 dpdklab
2023-10-20 9:42 dpdklab
2023-10-20 9:41 dpdklab
2023-10-20 9:41 dpdklab
2023-10-20 9:41 dpdklab
2023-10-20 9:41 dpdklab
2023-10-20 9:40 dpdklab
2023-10-20 9:40 dpdklab
2023-10-20 9:40 dpdklab
2023-10-20 9:40 dpdklab
2023-10-20 9:40 dpdklab
2023-10-20 9:40 dpdklab
2023-10-20 9:39 dpdklab
2023-10-20 9:39 dpdklab
2023-10-20 9:38 dpdklab
2023-10-20 9:37 dpdklab
2023-10-20 9:32 dpdklab
2023-10-20 9:32 dpdklab
2023-10-20 9:32 dpdklab
2023-10-20 9:31 dpdklab
2023-10-20 9:30 dpdklab
2023-10-20 9:29 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=65324c02.920a0220.eb16.4a9fSMTPIN_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).