From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw128391 [PATCH] [v2] cryptodev: avoid algorithm strings n
Date: Fri, 09 Jun 2023 14:11:01 -0700 (PDT) [thread overview]
Message-ID: <64839565.050a0220.81088.c625SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-x86_64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/128391
_Testing PASS_
Submitter: liu xixin <liuxixin2020@outlook.com>
Date: Thursday, June 08 2023 08:03:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:55ead98d1de1b02fa563e822a67c7adc0361ddfb
128391 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26591/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-09 21:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 21:11 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-09 21:12 dpdklab
2023-06-09 21:11 dpdklab
2023-06-09 21:11 dpdklab
2023-06-09 9:19 dpdklab
2023-06-08 22:39 dpdklab
2023-06-08 22:38 dpdklab
2023-06-08 22:38 dpdklab
2023-06-08 22:35 dpdklab
2023-06-08 20:09 dpdklab
2023-06-08 20:02 dpdklab
2023-06-08 19:00 dpdklab
2023-06-08 16:34 dpdklab
2023-06-08 14:52 dpdklab
2023-06-08 14:40 dpdklab
2023-06-08 14:14 dpdklab
2023-06-08 14:10 dpdklab
2023-06-08 14:08 dpdklab
2023-06-08 14:08 dpdklab
2023-06-08 14:03 dpdklab
2023-06-08 14:03 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=64839565.050a0220.81088.c625SMTPIN_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).