From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Chengwen Feng <fengchengwen@huawei.com>,
dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124600-124602 [PATCH] [5/5] app/testpmd: add error recovery usage demo
Date: Wed, 1 Mar 2023 04:30:06 +0000 (UTC) [thread overview]
Message-ID: <20230301043006.21A7D601B1@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-aarch64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/124602
_Testing PASS_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Wednesday, March 01 2023 03:06:10
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7710b5d15a014872a3aaf646668dafa928ca8473
124600-124602 --> testing pass
Test environment and result as below:
+----------------------+--------------+---------------------------+------------------------------+
| Environment | lpm_autotest | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest |
+======================+==============+===========================+==============================+
| Ubuntu 20.04 ARM SVE | PASS | SKIPPED | SKIPPED |
+----------------------+--------------+---------------------------+------------------------------+
| Debian 11 | SKIPPED | PASS | PASS |
+----------------------+--------------+---------------------------+------------------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Debian 11
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25570/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-01 4:30 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 4:30 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-02 3:21 dpdklab
2023-03-02 2:40 dpdklab
2023-03-02 2:35 dpdklab
2023-03-02 2:34 dpdklab
2023-03-02 2:30 dpdklab
2023-03-02 2:27 dpdklab
2023-03-02 2:27 dpdklab
2023-03-02 2:26 dpdklab
2023-03-02 2:24 dpdklab
2023-03-02 2:20 dpdklab
2023-03-02 2:13 dpdklab
2023-03-02 2:06 dpdklab
2023-03-02 2:03 dpdklab
2023-03-02 1:58 dpdklab
2023-03-02 1:45 dpdklab
2023-03-02 1:45 dpdklab
2023-03-02 1:29 dpdklab
2023-03-02 1:26 dpdklab
2023-03-01 13:20 dpdklab
2023-03-01 12:52 dpdklab
2023-03-01 12:00 dpdklab
2023-03-01 11:14 dpdklab
2023-03-01 10:39 dpdklab
2023-03-01 10:27 dpdklab
2023-03-01 10:07 dpdklab
2023-03-01 9:55 dpdklab
2023-03-01 9:01 dpdklab
2023-03-01 8:49 dpdklab
2023-03-01 8:33 dpdklab
2023-03-01 8:16 dpdklab
[not found] <20230301030610.49468-6-fengchengwen@huawei.com>
2023-03-01 8:07 ` |SUCCESS| pw124600-124602 [PATCH 5/5] " qemudev
2023-03-01 8:07 ` qemudev
2023-03-01 5:20 |SUCCESS| pw124600-124602 [PATCH] [5/5] " dpdklab
2023-03-01 5:12 dpdklab
2023-03-01 5:00 dpdklab
2023-03-01 4:48 dpdklab
2023-03-01 4:48 dpdklab
2023-03-01 4:43 dpdklab
2023-03-01 4:40 dpdklab
2023-03-01 4:29 dpdklab
2023-03-01 4:27 dpdklab
2023-03-01 4:24 dpdklab
2023-03-01 4:21 dpdklab
2023-03-01 4:21 dpdklab
2023-03-01 4:13 dpdklab
2023-03-01 4:10 dpdklab
2023-03-01 4:04 dpdklab
2023-03-01 4:01 dpdklab
2023-03-01 3: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=20230301043006.21A7D601B1@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=fengchengwen@huawei.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).