From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw127178 [PATCH] [v2] lib/cryptodev: fix assertion to remo
Date: Mon, 22 May 2023 14:14:14 -0700 (PDT) [thread overview]
Message-ID: <646bdb26.6b0a0220.943cd.11adSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-aarch64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/127178
_Testing PASS_
Submitter: Kamil Godzwon <kamilx.godzwon@intel.com>
Date: Monday, May 22 2023 19:04:52
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a399d7b5a994e335c446d4b15d7622d71dd8848c
127178 --> testing pass
Test environment and result as below:
+----------------------+---------------------------+------------------------------+--------------+
| Environment | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | lpm_autotest |
+======================+===========================+==============================+==============+
| Debian 11 | PASS | PASS | SKIPPED |
+----------------------+---------------------------+------------------------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | SKIPPED | PASS |
+----------------------+---------------------------+------------------------------+--------------+
Debian 11
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/26336/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-05-22 21:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 21:14 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-23 3:52 dpdklab
2023-05-23 3:42 dpdklab
2023-05-23 3:26 dpdklab
2023-05-23 3:21 dpdklab
2023-05-23 3:16 dpdklab
2023-05-22 22:33 dpdklab
2023-05-22 22:32 dpdklab
2023-05-22 22:23 dpdklab
2023-05-22 22:03 dpdklab
2023-05-22 21:36 dpdklab
2023-05-22 21:26 dpdklab
2023-05-22 21:15 dpdklab
2023-05-22 21:15 dpdklab
2023-05-22 21:03 dpdklab
2023-05-22 21:03 dpdklab
2023-05-22 21:02 dpdklab
2023-05-22 21:01 dpdklab
2023-05-22 20:59 dpdklab
2023-05-22 20:58 dpdklab
2023-05-22 20:47 dpdklab
2023-05-22 20:45 dpdklab
2023-05-22 20:24 dpdklab
2023-05-22 20:03 dpdklab
2023-05-22 20:01 dpdklab
2023-05-22 19:59 dpdklab
2023-05-22 19:55 dpdklab
2023-05-22 19:47 dpdklab
2023-05-22 19:45 dpdklab
2023-05-22 19:43 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=646bdb26.6b0a0220.943cd.11adSMTPIN_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).