From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137348 [PATCH] [v4] examples/ipsec-secgw: fix cryptodev
Date: Wed, 28 Feb 2024 01:27:45 -0800 (PST) [thread overview]
Message-ID: <65defc91.d40a0220.cbd13.58a9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240227132846.415698-1-radu.nicolau@intel.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137348
_Testing PASS_
Submitter: Radu Nicolau <radu.nicolau@intel.com>
Date: Tuesday, February 27 2024 13:28:46
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137348 --> testing pass
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29287/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-02-28 9:27 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240227132846.415698-1-radu.nicolau@intel.com>
2024-02-27 13:06 ` |SUCCESS| pw137348 [PATCH v4] examples/ipsec-secgw: fix cryptodev to SA mapping qemudev
2024-02-27 13:10 ` qemudev
2024-02-27 13:29 ` |WARNING| " checkpatch
2024-02-27 14:25 ` |SUCCESS| " 0-day Robot
2024-02-27 20:23 ` |SUCCESS| pw137348 [PATCH] [v4] examples/ipsec-secgw: fix cryptodev dpdklab
2024-02-27 20:24 ` dpdklab
2024-02-27 20:29 ` dpdklab
2024-02-27 20:35 ` dpdklab
2024-02-27 20:37 ` dpdklab
2024-02-27 20:38 ` dpdklab
2024-02-27 20:40 ` dpdklab
2024-02-27 20:40 ` dpdklab
2024-02-27 20:40 ` dpdklab
2024-02-27 20:41 ` dpdklab
2024-02-27 20:41 ` dpdklab
2024-02-27 20:44 ` dpdklab
2024-02-27 20:44 ` dpdklab
2024-02-27 20:44 ` dpdklab
2024-02-27 20:45 ` dpdklab
2024-02-27 20:48 ` |FAILURE| " dpdklab
2024-02-27 20:48 ` dpdklab
2024-02-27 20:49 ` dpdklab
2024-02-27 20:49 ` dpdklab
2024-02-27 20:49 ` dpdklab
2024-02-27 20:53 ` dpdklab
2024-02-27 20:53 ` |SUCCESS| " dpdklab
2024-02-27 20:54 ` |FAILURE| " dpdklab
2024-02-27 20:54 ` |SUCCESS| " dpdklab
2024-02-27 20:54 ` |FAILURE| " dpdklab
2024-02-27 20:55 ` dpdklab
2024-02-27 20:56 ` |SUCCESS| " dpdklab
2024-02-27 20:56 ` dpdklab
2024-02-27 20:56 ` dpdklab
2024-02-27 20:57 ` dpdklab
2024-02-27 20:57 ` dpdklab
2024-02-27 20:58 ` dpdklab
2024-02-27 20:58 ` dpdklab
2024-02-27 21:00 ` dpdklab
2024-02-27 21:01 ` dpdklab
2024-02-27 21:03 ` dpdklab
2024-02-27 21:03 ` dpdklab
2024-02-27 21:03 ` dpdklab
2024-02-27 21:03 ` dpdklab
2024-02-27 21:03 ` dpdklab
2024-02-27 21:04 ` dpdklab
2024-02-27 21:17 ` |FAILURE| " dpdklab
2024-02-27 21:33 ` |SUCCESS| " dpdklab
2024-02-27 23:33 ` dpdklab
2024-02-27 23:51 ` dpdklab
2024-02-28 2:42 ` |FAILURE| " dpdklab
2024-02-28 7:21 ` |SUCCESS| " dpdklab
2024-02-28 7:42 ` dpdklab
2024-02-28 9:27 ` dpdklab [this message]
2024-02-28 18:32 ` dpdklab
2024-02-29 11:06 ` dpdklab
2024-02-29 11:11 ` dpdklab
2024-02-29 11:19 ` dpdklab
2024-02-29 11:33 ` dpdklab
2024-02-27 16:56 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-02-27 16:54 dpdklab
2024-02-27 16:53 dpdklab
2024-02-27 16:52 dpdklab
2024-02-27 16:52 dpdklab
2024-02-27 16:52 dpdklab
2024-02-27 16:51 dpdklab
2024-02-27 16:47 dpdklab
2024-02-27 16:42 dpdklab
2024-02-27 16:41 dpdklab
2024-02-27 16:34 dpdklab
2024-02-27 16:07 dpdklab
2024-02-27 15:59 dpdklab
2024-02-27 15:56 dpdklab
2024-02-27 15:45 dpdklab
2024-02-27 15:33 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=65defc91.d40a0220.cbd13.58a9SMTPIN_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).