From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>, Kai Ji <kai.ji@intel.com>
Subject: |WARNING| pw125084-125085 [PATCH] [v1, 2/2] app/test: add ecdh test cases
Date: Wed, 15 Mar 2023 03:49:07 +0000 (UTC) [thread overview]
Message-ID: <20230315034907.6D0226011D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/125085
_Testing issues_
Submitter: Kai Ji <kai.ji@intel.com>
Date: Tuesday, March 14 2023 00:12:02
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:baf13c3135d0c5998fff7edc23fb89412dc89246
125084-125085 --> 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): ====
[3209/3226] Compiling C object 'app/test/3062f5d@@dpdk-test@exe/test_event_eth_tx_adapter.c.o'.
[3210/3226] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_sha.c.o'.
[3211/3226] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_xts.c.o'.
[3212/3226] Compiling C object 'app/test/3062f5d@@dpdk-test@exe/test_pcapng.c.o'.
[3213/3226] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation.c.o'.
[3214/3226] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_ccm.c.o'.
[3215/3226] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_ecdsa.c.o'.
[3216/3226] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_rsa.c.o'.
[3217/3226] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_tdes.c.o'.
[3218/3226] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_aes.c.o'.
[3219/3226] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_dev_self_test.c.o'.
[3220/3226] Compiling C object 'app/test/3062f5d@@dpdk-test@exe/test_trace_perf.c.o'.
[3221/3226] Compiling C object 'app/test/3062f5d@@dpdk-test@exe/test_compressdev.c.o'.
[3222/3226] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_main.c.o'.
[3223/3226] Compiling C object 'app/test/3062f5d@@dpdk-test@exe/test_ring_perf.c.o'.
[3224/3226] Linking target examples/dpdk-fips_validation.
[3225/3226] Compiling C object 'app/test/3062f5d@@dpdk-test@exe/test_ring.c.o'.
[3226/3226] Linking target app/test/dpdk-test.
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/patchsets/25721/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
reply other threads:[~2023-03-15 3:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230315034907.6D0226011D@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=kai.ji@intel.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).