From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@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] bbc9320cafa6e70d08fa80cf1e43da461aecb9f6
Date: Sun, 07 Jan 2024 23:49:38 -0800 (PST) [thread overview]
Message-ID: <659ba912.170a0220.419a5.b00cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing issues_
Branch: tags/v21.11
bbc9320cafa6e70d08fa80cf1e43da461aecb9f6 --> 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 drivers/librte_event_octeontx2.so.22.0.
[3080/3097] Linking target app/dpdk-test-pipeline.
[3081/3097] Linking target app/dpdk-test-crypto-perf.
[3082/3097] Linking target app/dpdk-dumpcap.
[3083/3097] Linking target app/dpdk-test-eventdev.
[3084/3097] Linking target app/dpdk-test-bbdev.
[3085/3097] Linking target app/dpdk-test-fib.
[3086/3097] Linking target app/test/dpdk-test.
[3087/3097] Linking target app/dpdk-test-flow-perf.
[3088/3097] Linking target app/dpdk-test-cmdline.
[3089/3097] Linking target app/dpdk-pdump.
[3090/3097] Linking target app/dpdk-test-regex.
[3091/3097] Linking target app/dpdk-proc-info.
[3092/3097] Linking target app/dpdk-test-sad.
[3093/3097] Linking target app/dpdk-test-compress-perf.
[3094/3097] Linking target app/dpdk-testpmd.
[3095/3097] Linking target app/dpdk-test-gpudev.
[3096/3097] Linking target app/dpdk-test-acl.
[3097/3097] Linking target examples/dpdk-fips_validation.
Processing file ../out/acvp-aes-cbc-vectors.json... Processing file ../out/cmac-aes-vectors.json... Processing file ../out/acvp-aes-gmac-vectors.json... Processing file ../out/hmac-sha-1-vectors.json... Processing file ../out/acvp-tdes-cbc-vectors.json... Processing file ../out/acvp-aes-ctr-vectors.json...
==== End log output ====
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27600/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-08 7:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 7:49 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-17 10:02 dpdklab
2024-01-17 7:28 dpdklab
2024-01-17 2:32 dpdklab
2024-01-12 6:14 dpdklab
2024-01-11 5:57 dpdklab
2024-01-10 5:53 dpdklab
2024-01-09 7:00 dpdklab
2024-01-07 6:44 dpdklab
2024-01-06 9:20 dpdklab
2024-01-05 6:22 dpdklab
2024-01-04 18:01 dpdklab
2024-01-03 9:40 dpdklab
2024-01-02 6:22 dpdklab
2024-01-01 5:48 dpdklab
2023-12-31 6:53 dpdklab
2023-12-30 7:00 dpdklab
2023-12-29 7:18 dpdklab
2023-12-28 7:05 dpdklab
2023-12-27 7:39 dpdklab
2023-12-26 6:03 dpdklab
2023-12-25 7:02 dpdklab
2023-12-24 6:39 dpdklab
2023-12-23 8:12 dpdklab
2023-12-22 17:27 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=659ba912.170a0220.419a5.b00cSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dpdk-test-reports@iol.unh.edu \
--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).