From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132257-132258 [PATCH] [v4,3/3] mldev: drop input and out
Date: Mon, 02 Oct 2023 05:44:28 -0700 (PDT) [thread overview]
Message-ID: <651abb2c.050a0220.81ad2.6955SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132258
_Testing PASS_
Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Monday, October 02 2023 09:58:58
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6e999364a6afb9189029154b1ac55b4ad5fb9b3f
132257-132258 --> testing pass
Test environment and result as below:
+----------------------+---------------------------+------------------------------+--------------+
| Environment | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | lpm_autotest |
+======================+===========================+==============================+==============+
| Debian 11 (arm) | PASS | PASS | SKIPPED |
+----------------------+---------------------------+------------------------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | SKIPPED | PASS |
+----------------------+---------------------------+------------------------------+--------------+
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.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/27800/
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-02 12:44 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 12:44 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-02 13:48 dpdklab
2023-10-02 13:33 dpdklab
2023-10-02 13:05 dpdklab
2023-10-02 13:05 dpdklab
2023-10-02 13:04 dpdklab
2023-10-02 13:01 dpdklab
2023-10-02 12:57 dpdklab
2023-10-02 12:54 dpdklab
2023-10-02 12:54 dpdklab
2023-10-02 12:50 dpdklab
2023-10-02 12:49 dpdklab
2023-10-02 12:47 dpdklab
2023-10-02 12:47 dpdklab
2023-10-02 12:46 dpdklab
2023-10-02 12:43 dpdklab
2023-10-02 12:41 dpdklab
2023-10-02 12:41 dpdklab
2023-10-02 12:41 dpdklab
2023-10-02 12:41 dpdklab
2023-10-02 12:38 dpdklab
2023-10-02 12:38 dpdklab
2023-10-02 12:38 dpdklab
2023-10-02 12:34 dpdklab
2023-10-02 12:34 dpdklab
2023-10-02 12:34 dpdklab
2023-10-02 12:34 dpdklab
2023-10-02 12:33 dpdklab
2023-10-02 12:33 dpdklab
2023-10-02 12:33 dpdklab
2023-10-02 12:33 dpdklab
2023-10-02 12:33 dpdklab
2023-10-02 12:32 dpdklab
2023-10-02 12:32 dpdklab
2023-10-02 12:32 dpdklab
2023-10-02 12:32 dpdklab
2023-10-02 12:32 dpdklab
2023-10-02 12:32 dpdklab
2023-10-02 12:32 dpdklab
2023-10-02 12:32 dpdklab
2023-10-02 12:32 dpdklab
2023-10-02 12:32 dpdklab
2023-10-02 12:29 dpdklab
2023-10-02 12:29 dpdklab
2023-10-02 12:29 dpdklab
2023-10-02 12:29 dpdklab
2023-10-02 12:28 dpdklab
2023-10-02 12:28 dpdklab
2023-10-02 12:28 dpdklab
2023-10-02 12:28 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=651abb2c.050a0220.81ad2.6955SMTPIN_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).