From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Chengwen Feng <fengchengwen@huawei.com>, dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133121 [PATCH] eal: support lcore usage ratio
Date: Sun, 22 Oct 2023 23:06:46 -0700 (PDT) [thread overview]
Message-ID: <65360d76.810a0220.6ab08.1717SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133121
_Testing PASS_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Monday, October 23 2023 04:08:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2cd2cf0cc53a508c4bd951a980ec534a646260de
133121 --> testing pass
Test environment and result as below:
+--------------------------+----------------+---------------------------+
| Environment | dpdk_unit_test | cryptodev_sw_zuc_autotest |
+==========================+================+===========================+
| Debian 11 (Buster) (ARM) | PASS | SKIPPED |
+--------------------------+----------------+---------------------------+
| Fedora 37 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+---------------------------+
| Fedora 38 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+---------------------------+
| CentOS Stream 9 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+---------------------------+
| Debian 11 (arm) | SKIPPED | PASS |
+--------------------------+----------------+---------------------------+
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
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
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28028/
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-23 6:06 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 6:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-23 9:01 dpdklab
2023-10-23 8:22 dpdklab
2023-10-23 8:09 dpdklab
2023-10-23 8:07 dpdklab
2023-10-23 7:58 dpdklab
2023-10-23 7:57 dpdklab
2023-10-23 7:56 dpdklab
2023-10-23 7:55 dpdklab
2023-10-23 7:54 dpdklab
2023-10-23 7:46 dpdklab
2023-10-23 7:44 dpdklab
2023-10-23 7:40 dpdklab
2023-10-23 7:39 dpdklab
2023-10-23 7:38 dpdklab
2023-10-23 7:37 dpdklab
2023-10-23 7:37 dpdklab
2023-10-23 7:36 dpdklab
2023-10-23 7:33 dpdklab
2023-10-23 7:32 dpdklab
2023-10-23 7:32 dpdklab
2023-10-23 7:29 dpdklab
2023-10-23 7:27 dpdklab
2023-10-23 7:26 dpdklab
2023-10-23 7:25 dpdklab
2023-10-23 7:25 dpdklab
2023-10-23 7:18 dpdklab
2023-10-23 7:16 dpdklab
2023-10-23 7:16 dpdklab
2023-10-23 7:13 dpdklab
2023-10-23 7:12 dpdklab
2023-10-23 7:10 dpdklab
2023-10-23 7:08 dpdklab
2023-10-23 6:31 dpdklab
2023-10-23 6:15 dpdklab
2023-10-23 6:11 dpdklab
2023-10-23 6:09 dpdklab
2023-10-23 6:07 dpdklab
2023-10-23 6:06 dpdklab
2023-10-23 6:06 dpdklab
2023-10-23 6:05 dpdklab
2023-10-23 6:05 dpdklab
2023-10-23 6:04 dpdklab
2023-10-23 6:04 dpdklab
2023-10-23 6:03 dpdklab
2023-10-23 6:03 dpdklab
2023-10-23 6:03 dpdklab
2023-10-23 6:02 dpdklab
2023-10-23 6:01 dpdklab
2023-10-23 6:01 dpdklab
2023-10-23 6:00 dpdklab
2023-10-23 5:57 dpdklab
2023-10-23 5:49 dpdklab
2023-10-23 5:44 dpdklab
2023-10-23 5:43 dpdklab
[not found] <20231023040811.46038-1-fengchengwen@huawei.com>
2023-10-23 3:51 ` qemudev
2023-10-23 3:55 ` qemudev
2023-10-23 4:13 ` checkpatch
2023-10-23 4:59 ` 0-day Robot
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=65360d76.810a0220.6ab08.1717SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=fengchengwen@huawei.com \
--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).