From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Jeremy Spewock <jspewock@iol.unh.edu>
Subject: |WARNING| pw135901 [PATCH] [v4] dts: add Dockerfile
Date: Fri, 19 Jan 2024 04:32:38 -0800 (PST) [thread overview]
Message-ID: <65aa6be6.050a0220.6c953.a84cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-sample-apps-testing
Test-Status: WARNING
http://dpdk.org/patch/135901
_Testing issues_
Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Tuesday, January 16 2024 19:18:14
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d4af9a82063e4c39568191eaa12955d3ca39581a
135901 --> 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): ====
[2801/2816] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_xts.c.o'.
[2802/2816] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_gcm.c.o'.
[2803/2816] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_cmac.c.o'.
[2804/2816] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_ccm.c.o'.
[2805/2816] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_sha.c.o'.
[2806/2816] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_ecdsa.c.o'.
[2807/2816] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_rsa.c.o'.
[2808/2816] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_table_combined.c.o'.
[2809/2816] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_dev_self_test.c.o'.
[2810/2816] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_tdes.c.o'.
[2811/2816] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_main.c.o'.
[2812/2816] Linking target examples/dpdk-fips_validation.
[2813/2816] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_ring_perf.c.o'.
[2814/2816] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_trace_perf.c.o'.
[2815/2816] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_ring.c.o'.
[2816/2816] Linking target app/dpdk-test.
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/patchsets/28879/
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-19 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 12:32 dpdklab [this message]
[not found] <20240116191814.31316-1-jspewock@iol.unh.edu>
2024-01-16 19:19 ` |WARNING| pw135901 [PATCH v4] " checkpatch
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=65aa6be6.050a0220.6c953.a84cSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=jspewock@iol.unh.edu \
--cc=test-report@dpdk.org \
/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).