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] d75b66ad1cf8b9c0a14020a4cd9ddcd34dea924b
Date: Sat, 12 Aug 2023 07:46:10 -0700 (PDT) [thread overview]
Message-ID: <64d79b32.810a0220.77e40.c980SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing issues_
Branch: tags/v22.11
d75b66ad1cf8b9c0a14020a4cd9ddcd34dea924b --> 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): ====
[3519/3533] Linking target app/dpdk-test-regex.
[3520/3533] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_xts.c.o'.
[3521/3533] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation.c.o'.
[3522/3533] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_ecdsa.c.o'.
[3523/3533] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_tdes.c.o'.
[3524/3533] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_rsa.c.o'.
[3525/3533] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_gcm.c.o'.
[3526/3533] Linking target app/dpdk-testpmd.
[3527/3533] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_dev_self_test.c.o'.
[3528/3533] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_main.c.o'.
[3529/3533] Compiling C object 'app/test/3062f5d@@dpdk-test@exe/test_compressdev.c.o'.
[3530/3533] Compiling C object 'app/test/3062f5d@@dpdk-test@exe/test_ring_perf.c.o'.
[3531/3533] Linking target examples/dpdk-fips_validation.
[3532/3533] Compiling C object 'app/test/3062f5d@@dpdk-test@exe/test_ring.c.o'.
[3533/3533] Linking target app/test/dpdk-test.
Processing file ../out/acvp-aes-cbc-vectors.json... 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: 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/25796/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-12 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 14:46 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-29 23:06 dpdklab
2023-07-25 11:36 dpdklab
2023-06-18 23:05 dpdklab
2023-06-17 15:35 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=64d79b32.810a0220.77e40.c980SMTPIN_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).