From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw128629-128630 [PATCH] [v3,2/2] build: change libfdt flag
Date: Tue, 13 Jun 2023 20:01:44 -0700 (PDT) [thread overview]
Message-ID: <64892d98.050a0220.d1fd4.b8b1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/128630
_Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Tuesday, June 13 2023 15:33:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:050de60d8a5cef8b7c10b4471905ca8bf69d670e
128629-128630 --> testing pass
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26665/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-14 3:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 3:01 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-14 23:58 dpdklab
2023-06-14 8:19 dpdklab
2023-06-14 8:16 dpdklab
2023-06-14 3:02 dpdklab
2023-06-13 20:16 dpdklab
2023-06-13 18:12 dpdklab
2023-06-13 18:04 dpdklab
2023-06-13 18:02 dpdklab
2023-06-13 18:00 dpdklab
2023-06-13 17:59 dpdklab
2023-06-13 17:57 dpdklab
2023-06-13 17:51 dpdklab
2023-06-13 17:51 dpdklab
2023-06-13 17:44 dpdklab
2023-06-13 17:40 dpdklab
2023-06-13 17:40 dpdklab
2023-06-13 17:02 dpdklab
2023-06-13 17:01 dpdklab
2023-06-13 16:38 dpdklab
2023-06-13 16:28 dpdklab
2023-06-13 16:28 dpdklab
2023-06-13 16:28 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=64892d98.050a0220.d1fd4.b8b1SMTPIN_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).