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] 74f84c75584a043cbc7f983579083f01f8b7d225
Date: Wed, 22 Feb 2023 20:54:59 +0000 (UTC) [thread overview]
Message-ID: <20230222205459.87E31601B4@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1753 bytes --]
_Testing issues_
Branch: 21.11-staging
74f84c75584a043cbc7f983579083f01f8b7d225 --> 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): ====
[3079/3097] Linking target app/dpdk-proc-info.
[3080/3097] Linking target app/dpdk-test-flow-perf.
[3081/3097] Linking target drivers/librte_event_octeontx2.so.22.0.
[3082/3097] Linking target app/test/dpdk-test.
[3083/3097] Linking target app/dpdk-dumpcap.
[3084/3097] Linking target app/dpdk-test-cmdline.
[3085/3097] Linking target app/dpdk-pdump.
[3086/3097] Linking target app/dpdk-test-crypto-perf.
[3087/3097] Linking target app/dpdk-test-regex.
[3088/3097] Linking target app/dpdk-test-gpudev.
[3089/3097] Linking target app/dpdk-test-compress-perf.
[3090/3097] Linking target app/dpdk-test-acl.
[3091/3097] Linking target app/dpdk-test-fib.
[3092/3097] Linking target app/dpdk-test-pipeline.
[3093/3097] Linking target app/dpdk-test-eventdev.
[3094/3097] Linking target app/dpdk-testpmd.
[3095/3097] Linking target app/dpdk-test-sad.
[3096/3097] Linking target app/dpdk-test-bbdev.
[3097/3097] Linking target examples/dpdk-fips_validation.
Processing file ../out/acvp-aes-cbc-vectors.json...
==== 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/23460/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-22 20:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 20:54 dpdklab [this message]
2023-03-01 10:25 dpdklab
2023-03-02 7:00 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=20230222205459.87E31601B4@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).