From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw131184 [PATCH] [v3] net/ice: fix tm configuration cannot
Date: Wed, 06 Sep 2023 02:02:51 -0700 (PDT) [thread overview]
Message-ID: <64f8403b.920a0220.36883.d24dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/131184
_Testing PASS_
Submitter: Kaiwen Deng <kaiwenx.deng@intel.com>
Date: Wednesday, September 06 2023 07:49:30
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e92ba1426914db1d224dd5e9a1743657681b8814
131184 --> testing pass
Test environment and result as below:
+--------------------------+--------------------+
| Environment | dpdk_meson_compile |
+==========================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+--------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+--------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+--------------------------+--------------------+
| CentOS Stream 9 (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 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27532/
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-06 9:02 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 9:02 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-06 10:30 dpdklab
2023-09-06 10:16 dpdklab
2023-09-06 10:11 dpdklab
2023-09-06 10:07 dpdklab
2023-09-06 10:01 dpdklab
2023-09-06 9:57 dpdklab
2023-09-06 9:57 dpdklab
2023-09-06 9:46 dpdklab
2023-09-06 9:43 dpdklab
2023-09-06 9:41 dpdklab
2023-09-06 9:36 dpdklab
2023-09-06 9:36 dpdklab
2023-09-06 9:32 dpdklab
2023-09-06 9:32 dpdklab
2023-09-06 9:25 dpdklab
2023-09-06 9:23 dpdklab
2023-09-06 9:23 dpdklab
2023-09-06 9:21 dpdklab
2023-09-06 9:20 dpdklab
2023-09-06 9:18 dpdklab
2023-09-06 9:16 dpdklab
2023-09-06 9:14 dpdklab
2023-09-06 9:13 dpdklab
2023-09-06 9:11 dpdklab
2023-09-06 9:10 dpdklab
2023-09-06 9:09 dpdklab
2023-09-06 9:08 dpdklab
2023-09-06 9:06 dpdklab
2023-09-06 9:05 dpdklab
2023-09-06 9:05 dpdklab
2023-09-06 9:05 dpdklab
2023-09-06 9:05 dpdklab
2023-09-06 9:05 dpdklab
2023-09-06 9:04 dpdklab
2023-09-06 9:04 dpdklab
2023-09-06 9:04 dpdklab
2023-09-06 9:03 dpdklab
2023-09-06 9:03 dpdklab
2023-09-06 9:03 dpdklab
2023-09-06 9:03 dpdklab
2023-09-06 9:03 dpdklab
2023-09-06 9:03 dpdklab
2023-09-06 9:03 dpdklab
2023-09-06 9:02 dpdklab
2023-09-06 9:02 dpdklab
2023-09-06 9:01 dpdklab
2023-09-06 9:00 dpdklab
2023-09-06 9:00 dpdklab
2023-09-06 8:59 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=64f8403b.920a0220.36883.d24dSMTPIN_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).