From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw126954-126957 [PATCH] [4/4] app/test: add rsa kat and pwct tests
Date: Wed, 17 May 2023 15:55:20 -0700 (PDT) [thread overview]
Message-ID: <64655b58.050a0220.c0da2.047eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/126957
_Testing PASS_
Submitter: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Date: Wednesday, May 17 2023 21:19:00
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a399d7b5a994e335c446d4b15d7622d71dd8848c
126954-126957 --> testing pass
Test environment and result as below:
+-------------+----------+
| Environment | abi_test |
+=============+==========+
| RHEL8 | PASS |
+-------------+----------+
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26268/
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-17 22:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 22:55 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-18 3:45 dpdklab
2023-05-17 23:36 dpdklab
2023-05-17 23:15 dpdklab
2023-05-17 23:12 dpdklab
2023-05-17 23:11 dpdklab
2023-05-17 23:02 dpdklab
2023-05-17 23:02 dpdklab
2023-05-17 22:59 dpdklab
2023-05-17 22:51 dpdklab
2023-05-17 22:51 dpdklab
2023-05-17 22:51 dpdklab
2023-05-17 22:49 dpdklab
2023-05-17 22:46 dpdklab
2023-05-17 22:44 dpdklab
2023-05-17 22:44 dpdklab
[not found] <20230517211900.926163-5-arkadiuszx.kusztal@intel.com>
2023-05-17 21:08 ` |SUCCESS| pw126954-126957 [PATCH 4/4] " qemudev
2023-05-17 21:12 ` qemudev
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=64655b58.050a0220.c0da2.047eSMTPIN_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).