From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |WARNING| [GIT MASTER] 9dae7a15aea76313c592c11db44e1386e85f86fe
Date: Wed, 5 Apr 2023 05:24:27 +0000 (UTC) [thread overview]
Message-ID: <20230405052427.0D09F6012C@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
_Testing issues_
Branch: tags/v22.11
9dae7a15aea76313c592c11db44e1386e85f86fe --> testing fail
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | WARN |
+--------------+----------------------+
==== 20 line log output for Ubuntu 20.04 (dpdk_fips_validation): ====
[3521/3534] Linking target app/dpdk-test-compress-perf.
[3522/3534] Linking target app/dpdk-test-cmdline.
[3523/3534] Linking target app/dpdk-dumpcap.
[3524/3534] Linking target app/dpdk-testpmd.
[3525/3534] Linking target app/dpdk-test-acl.
[3526/3534] Linking target app/dpdk-test-regex.
[3527/3534] Linking target app/dpdk-test-gpudev.
[3528/3534] Linking target app/dpdk-test-sad.
[3529/3534] Linking target app/dpdk-test-pipeline.
[3530/3534] Linking target app/dpdk-test-security-perf.
[3531/3534] Linking target app/dpdk-test-flow-perf.
[3532/3534] Linking target examples/dpdk-fips_validation.
[3533/3534] Compiling C object 'app/test/3062f5d@@dpdk-test@exe/test_ring.c.o'.
[3534/3534] Linking target app/test/dpdk-test.
Processing file ../out/acvp-aes-cbc-vectors.json... Done
Processing file ../out/cmac-aes-vectors.json... Done
Processing file ../out/acvp-aes-gmac-vectors.json... Done
Processing file ../out/hmac-sha-1-vectors.json... Done
Processing file ../out/acvp-tdes-cbc-vectors.json... Done
Processing file ../out/acvp-aes-ctr-vectors.json... Done
==== End log output ====
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/tarballs/24145/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-05 5:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 5:24 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-31 18:41 dpdklab
2023-03-09 7:57 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=20230405052427.0D09F6012C@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).