From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw150367-150368 [PATCH] [2/2] net/nfp: support load firmwa
Date: Wed, 22 Jan 2025 12:15:51 -0800 (PST) [thread overview]
Message-ID: <679151f7.d40a0220.e8e15.1b69SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250122014751.1706413-3-chaoyong.he@corigine.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/150368
_Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Wednesday, January 22 2025 01:47:51
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:347a988b93e7b63b27f1dfa09bd03318d810a9a9
150367-150368 --> testing pass
Upstream job id: ACVP-FIPS-testing#8643
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
Ubuntu 20.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32392/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2025-01-22 20:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250122014751.1706413-3-chaoyong.he@corigine.com>
2025-01-22 1:27 ` |SUCCESS| pw150367-150368 [PATCH 2/2] net/nfp: support load firmware for card without DDR qemudev
2025-01-22 1:31 ` qemudev
2025-01-22 1:48 ` |SUCCESS| pw150368 " checkpatch
2025-01-22 3:04 ` 0-day Robot
2025-01-22 10:10 ` |PENDING| pw150367-150368 [PATCH] [2/2] net/nfp: support load firmwa dpdklab
2025-01-22 11:05 ` dpdklab
2025-01-22 11:15 ` dpdklab
2025-01-22 11:31 ` |SUCCESS| " dpdklab
2025-01-22 11:59 ` dpdklab
2025-01-22 12:51 ` dpdklab
2025-01-22 14:05 ` |WARNING| " dpdklab
2025-01-22 20:15 ` dpdklab [this message]
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=679151f7.d40a0220.e8e15.1b69SMTPIN_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).