From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134505 [PATCH] [v1] test/crypto: fix timeout in Rx injec
Date: Tue, 21 Nov 2023 00:07:06 -0800 (PST) [thread overview]
Message-ID: <655c652a.050a0220.2dcd.dab7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/134505
_Testing PASS_
Submitter: Vidya Sagar Velumuri <vvelumuri@marvell.com>
Date: Tuesday, November 21 2023 06:49:51
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:517b4b26b508a6464d07c456c04eb48d6c7f03ea
134505 --> testing pass
Test environment and result as below:
+--------------------------+------------------------------+---------------------------+----------------+
| Environment | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest | dpdk_unit_test |
+==========================+==============================+===========================+================+
| Debian 11 (arm) | PASS | PASS | SKIPPED |
+--------------------------+------------------------------+---------------------------+----------------+
| CentOS Stream 9 (ARM) | SKIPPED | SKIPPED | PASS |
+--------------------------+------------------------------+---------------------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED | SKIPPED | PASS |
+--------------------------+------------------------------+---------------------------+----------------+
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28425/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-21 8:07 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 8:07 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-21 9:30 dpdklab
2023-11-21 9:24 dpdklab
2023-11-21 9:22 dpdklab
2023-11-21 9:21 dpdklab
2023-11-21 8:48 dpdklab
2023-11-21 8:44 dpdklab
2023-11-21 8:42 dpdklab
2023-11-21 8:42 dpdklab
2023-11-21 8:33 dpdklab
2023-11-21 8:33 dpdklab
2023-11-21 8:32 dpdklab
2023-11-21 8:31 dpdklab
2023-11-21 8:29 dpdklab
2023-11-21 8:27 dpdklab
2023-11-21 8:27 dpdklab
2023-11-21 8:22 dpdklab
2023-11-21 8:21 dpdklab
2023-11-21 8:19 dpdklab
2023-11-21 8:19 dpdklab
2023-11-21 8:17 dpdklab
2023-11-21 8:17 dpdklab
2023-11-21 8:16 dpdklab
2023-11-21 8:16 dpdklab
2023-11-21 8:16 dpdklab
2023-11-21 8:15 dpdklab
2023-11-21 8:14 dpdklab
2023-11-21 8:13 dpdklab
2023-11-21 8:13 dpdklab
2023-11-21 8:13 dpdklab
2023-11-21 8:13 dpdklab
2023-11-21 8:11 dpdklab
2023-11-21 8:11 dpdklab
2023-11-21 8:10 dpdklab
2023-11-21 8:09 dpdklab
2023-11-21 8:08 dpdklab
2023-11-21 8:07 dpdklab
2023-11-21 8:06 dpdklab
2023-11-21 8:06 dpdklab
2023-11-21 8:06 dpdklab
2023-11-21 8:06 dpdklab
2023-11-21 8:06 dpdklab
2023-11-21 8:06 dpdklab
2023-11-21 8:05 dpdklab
2023-11-21 8:05 dpdklab
2023-11-21 8:05 dpdklab
2023-11-21 8:04 dpdklab
2023-11-21 8:04 dpdklab
2023-11-21 8:04 dpdklab
2023-11-21 8:04 dpdklab
2023-11-21 8:04 dpdklab
2023-11-21 8:03 dpdklab
2023-11-21 8:03 dpdklab
2023-11-21 8:03 dpdklab
2023-11-21 8:02 dpdklab
2023-11-21 8:02 dpdklab
2023-11-21 8:02 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=655c652a.050a0220.2dcd.dab7SMTPIN_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).