From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw154051-154053 [PATCH] [v4,3/3] riscv: override machine_a
Date: Thu, 05 Jun 2025 18:05:16 -0700 (PDT) [thread overview]
Message-ID: <68423ecc.050a0220.316a2d.16d9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <tencent_0061818419F294AB7658400E45142FCC010A@qq.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/154053
_Testing PASS_
Submitter: None <uk7b@foxmail.com>
Date: Thursday, June 05 2025 10:58:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3c440cdfe87a2925af1be023e66bdf0bffc423a4
154051-154053 --> testing pass
Upstream job id: ACVP-FIPS-testing#10039
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
Ubuntu 20.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33330/
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-06-06 1:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_0061818419F294AB7658400E45142FCC010A@qq.com>
2025-06-05 10:33 ` |SUCCESS| pw154051-154053 [PATCH v4 3/3] riscv: override machine_args only when default qemudev
2025-06-05 10:37 ` qemudev
2025-06-05 10:58 ` |SUCCESS| pw154053 " checkpatch
2025-06-05 12:24 ` 0-day Robot
2025-06-05 14:31 ` |PENDING| pw154051-154053 [PATCH] [v4,3/3] riscv: override machine_a dpdklab
2025-06-05 15:16 ` dpdklab
2025-06-05 17:55 ` |SUCCESS| " dpdklab
2025-06-05 21:59 ` dpdklab
2025-06-05 23:30 ` dpdklab
2025-06-06 1:05 ` 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=68423ecc.050a0220.316a2d.16d9SMTPIN_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).