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| pw133058 [PATCH] dmadev: add tracepoints at control path A
Date: Thu, 19 Oct 2023 20:07:56 -0700 (PDT) [thread overview]
Message-ID: <6531ef0c.050a0220.dee53.2887SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133058
_Testing PASS_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Friday, October 20 2023 02:21:36
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2cd2cf0cc53a508c4bd951a980ec534a646260de
133058 --> testing pass
Test environment and result as below:
+--------------------------+----------------+------------------------------+
| Environment | dpdk_unit_test | cryptodev_sw_snow3g_autotest |
+==========================+================+==============================+
| Debian 11 (Buster) (ARM) | PASS | SKIPPED |
+--------------------------+----------------+------------------------------+
| Fedora 38 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+------------------------------+
| CentOS Stream 9 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+------------------------------+
| Fedora 37 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+------------------------------+
| Debian 11 (arm) | SKIPPED | PASS |
+--------------------------+----------------+------------------------------+
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
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.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/28015/
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 3:08 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 3:07 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-20 20:48 dpdklab
2023-10-20 4:28 dpdklab
2023-10-20 3:38 dpdklab
2023-10-20 3:35 dpdklab
2023-10-20 3:33 dpdklab
2023-10-20 3:32 dpdklab
2023-10-20 3:32 dpdklab
2023-10-20 3:31 dpdklab
2023-10-20 3:31 dpdklab
2023-10-20 3:30 dpdklab
2023-10-20 3:29 dpdklab
2023-10-20 3:28 dpdklab
2023-10-20 3:17 dpdklab
2023-10-20 3:17 dpdklab
2023-10-20 3:13 dpdklab
2023-10-20 3:10 dpdklab
2023-10-20 3:10 dpdklab
2023-10-20 3:10 dpdklab
2023-10-20 3:07 dpdklab
2023-10-20 3:07 dpdklab
2023-10-20 3:07 dpdklab
2023-10-20 3:07 dpdklab
2023-10-20 3:07 dpdklab
2023-10-20 3:07 dpdklab
2023-10-20 3:07 dpdklab
2023-10-20 3:07 dpdklab
2023-10-20 3:07 dpdklab
2023-10-20 3:07 dpdklab
2023-10-20 3:07 dpdklab
2023-10-20 3:05 dpdklab
2023-10-20 3:05 dpdklab
2023-10-20 3:05 dpdklab
2023-10-20 3:05 dpdklab
2023-10-20 3:05 dpdklab
2023-10-20 3:05 dpdklab
2023-10-20 3:05 dpdklab
2023-10-20 3:05 dpdklab
2023-10-20 3:05 dpdklab
2023-10-20 3:04 dpdklab
2023-10-20 3:00 dpdklab
2023-10-20 3:00 dpdklab
2023-10-20 3:00 dpdklab
2023-10-20 2:59 dpdklab
2023-10-20 2:59 dpdklab
2023-10-20 2:59 dpdklab
2023-10-20 2:59 dpdklab
2023-10-20 2: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=6531ef0c.050a0220.dee53.2887SMTPIN_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).