From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138379-138383 [PATCH] [v8,5/5] config/arm: allow WFE to
Date: Thu, 14 Mar 2024 07:44:29 -0700 (PDT) [thread overview]
Message-ID: <65f30d4d.050a0220.d528c.289aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240314113829.2511-5-pbhagavatula@marvell.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138383
_Testing PASS_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Thursday, March 14 2024 11:38:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cd218549b686d6be394ef3b171eafa16c038bfe3
138379-138383 --> 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/29550/
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-03-14 14:44 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240314113829.2511-5-pbhagavatula@marvell.com>
2024-03-14 11:16 ` |SUCCESS| pw138379-138383 [PATCH v8 5/5] config/arm: allow WFE to be enabled config time qemudev
2024-03-14 11:20 ` qemudev
2024-03-14 11:40 ` |SUCCESS| pw138383 " checkpatch
2024-03-14 12:43 ` 0-day Robot
2024-03-14 12:54 ` |SUCCESS| pw138379-138383 [PATCH] [v8,5/5] config/arm: allow WFE to dpdklab
2024-03-14 12:56 ` dpdklab
2024-03-14 12:56 ` dpdklab
2024-03-14 12:57 ` dpdklab
2024-03-14 12:58 ` dpdklab
2024-03-14 12:58 ` dpdklab
2024-03-14 12:58 ` dpdklab
2024-03-14 12:59 ` dpdklab
2024-03-14 13:01 ` dpdklab
2024-03-14 13:02 ` dpdklab
2024-03-14 13:02 ` dpdklab
2024-03-14 13:04 ` dpdklab
2024-03-14 13:19 ` dpdklab
2024-03-14 13:20 ` dpdklab
2024-03-14 13:20 ` dpdklab
2024-03-14 13:20 ` dpdklab
2024-03-14 13:21 ` dpdklab
2024-03-14 13:21 ` dpdklab
2024-03-14 13:21 ` dpdklab
2024-03-14 13:22 ` dpdklab
2024-03-14 13:23 ` dpdklab
2024-03-14 13:23 ` dpdklab
2024-03-14 13:23 ` dpdklab
2024-03-14 13:23 ` dpdklab
2024-03-14 13:24 ` dpdklab
2024-03-14 13:24 ` dpdklab
2024-03-14 13:24 ` dpdklab
2024-03-14 13:25 ` dpdklab
2024-03-14 13:25 ` dpdklab
2024-03-14 13:25 ` dpdklab
2024-03-14 13:25 ` dpdklab
2024-03-14 13:25 ` dpdklab
2024-03-14 13:26 ` dpdklab
2024-03-14 13:26 ` dpdklab
2024-03-14 13:26 ` dpdklab
2024-03-14 13:26 ` dpdklab
2024-03-14 13:26 ` dpdklab
2024-03-14 13:27 ` dpdklab
2024-03-14 13:27 ` dpdklab
2024-03-14 13:27 ` dpdklab
2024-03-14 13:27 ` dpdklab
2024-03-14 13:28 ` dpdklab
2024-03-14 13:28 ` dpdklab
2024-03-14 13:28 ` dpdklab
2024-03-14 13:28 ` dpdklab
2024-03-14 13:29 ` dpdklab
2024-03-14 13:29 ` dpdklab
2024-03-14 13:29 ` dpdklab
2024-03-14 13:31 ` dpdklab
2024-03-14 13:31 ` dpdklab
2024-03-14 13:32 ` dpdklab
2024-03-14 13:32 ` dpdklab
2024-03-14 13:32 ` dpdklab
2024-03-14 13:36 ` dpdklab
2024-03-14 13:43 ` dpdklab
2024-03-14 13:45 ` dpdklab
2024-03-14 13:50 ` dpdklab
2024-03-14 13:53 ` dpdklab
2024-03-14 13:55 ` dpdklab
2024-03-14 13:58 ` dpdklab
2024-03-14 14:00 ` dpdklab
2024-03-14 14:07 ` dpdklab
2024-03-14 14:08 ` dpdklab
2024-03-14 14:14 ` dpdklab
2024-03-14 14:18 ` dpdklab
2024-03-14 14:27 ` dpdklab
2024-03-14 14:29 ` dpdklab
2024-03-14 14:37 ` dpdklab
2024-03-14 14:44 ` dpdklab [this message]
2024-03-14 14:50 ` dpdklab
2024-03-14 16:12 ` dpdklab
2024-03-18 7:37 ` dpdklab
2024-03-18 8:13 ` 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=65f30d4d.050a0220.d528c.289aSMTPIN_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).