From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133637 [PATCH] net/ice: fix DCF port statistics not clea
Date: Tue, 31 Oct 2023 02:37:32 -0700 (PDT) [thread overview]
Message-ID: <6540cadc.170a0220.6769f.2b4cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133637
_Testing PASS_
Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Tuesday, October 31 2023 07:04:26
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:32faaf30732cb4006cd1e45997403427029ef5fe
133637 --> testing pass
Test environment and result as below:
+--------------------------+------------------------------+---------------------------+----------------+--------------+
| Environment | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest | dpdk_unit_test | lpm_autotest |
+==========================+==============================+===========================+================+==============+
| Debian 11 (arm) | PASS | PASS | SKIPPED | SKIPPED |
+--------------------------+------------------------------+---------------------------+----------------+--------------+
| Debian 11 (Buster) (ARM) | SKIPPED | SKIPPED | PASS | SKIPPED |
+--------------------------+------------------------------+---------------------------+----------------+--------------+
| Fedora 38 (ARM) | SKIPPED | SKIPPED | PASS | SKIPPED |
+--------------------------+------------------------------+---------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | SKIPPED | SKIPPED | PASS |
+--------------------------+------------------------------+---------------------------+----------------+--------------+
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28153/
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-31 9:37 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 9:37 dpdklab [this message]
2023-10-31 9:37 dpdklab
2023-10-31 9:38 dpdklab
2023-10-31 9:40 dpdklab
2023-10-31 9:40 dpdklab
2023-10-31 9:42 dpdklab
2023-10-31 9:44 dpdklab
2023-10-31 9:45 dpdklab
2023-10-31 9:46 dpdklab
2023-10-31 9:46 dpdklab
2023-10-31 9:47 dpdklab
2023-10-31 9:48 dpdklab
2023-10-31 9:49 dpdklab
2023-10-31 9:49 dpdklab
2023-10-31 9:51 dpdklab
2023-10-31 9:52 dpdklab
2023-10-31 9:53 dpdklab
2023-10-31 9:53 dpdklab
2023-10-31 9:54 dpdklab
2023-10-31 9:54 dpdklab
2023-10-31 9:54 dpdklab
2023-10-31 9:55 dpdklab
2023-10-31 9:55 dpdklab
2023-10-31 9:55 dpdklab
2023-10-31 9:55 dpdklab
2023-10-31 9:56 dpdklab
2023-10-31 9:56 dpdklab
2023-10-31 9:56 dpdklab
2023-10-31 9:56 dpdklab
2023-10-31 9:56 dpdklab
2023-10-31 9:56 dpdklab
2023-10-31 9:56 dpdklab
2023-10-31 9:56 dpdklab
2023-10-31 9:56 dpdklab
2023-10-31 9:56 dpdklab
2023-10-31 9:56 dpdklab
2023-10-31 9:56 dpdklab
2023-10-31 9:56 dpdklab
2023-10-31 9:57 dpdklab
2023-10-31 9:57 dpdklab
2023-10-31 9:57 dpdklab
2023-10-31 9:57 dpdklab
2023-10-31 9:57 dpdklab
2023-10-31 9:57 dpdklab
2023-10-31 9:57 dpdklab
2023-10-31 9:57 dpdklab
2023-10-31 9:58 dpdklab
2023-10-31 9:58 dpdklab
2023-10-31 10:02 dpdklab
2023-10-31 10:06 dpdklab
2023-10-31 10:20 dpdklab
2023-10-31 10:24 dpdklab
2023-10-31 10:36 dpdklab
2023-10-31 13:13 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=6540cadc.170a0220.6769f.2b4cSMTPIN_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).