From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: |WARNING| pw137549-137564 [PATCH] [v5,22/22] devtools: forbid use ar
Date: Mon, 04 Mar 2024 03:17:58 -0800 (PST) [thread overview]
Message-ID: <65e5ade6.250a0220.47bd2.0cabSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1709242325-17218-23-git-send-email-roretzla@linux.microsoft.com>
Test-Label: iol-sample-apps-testing
Test-Status: WARNING
http://dpdk.org/patch/137564
_Testing issues_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Thursday, February 29 2024 21:32:05
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137549-137564 --> 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): ====
[2829/2845] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation.c.o'.
[2830/2845] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_aes.c.o'.
[2831/2845] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_sha.c.o'.
[2832/2845] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_xts.c.o'.
[2833/2845] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_ccm.c.o'.
[2834/2845] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_hmac.c.o'.
[2835/2845] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_rsa.c.o'.
[2836/2845] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_ecdsa.c.o'.
[2837/2845] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_table_combined.c.o'.
[2838/2845] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_tdes.c.o'.
[2839/2845] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_dev_self_test.c.o'.
[2840/2845] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_main.c.o'.
[2841/2845] Linking target examples/dpdk-fips_validation.
[2842/2845] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_trace_perf.c.o'.
[2843/2845] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_ring_perf.c.o'.
[2844/2845] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_ring.c.o'.
[2845/2845] Linking target app/dpdk-test.
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... 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/29352/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2024-03-04 11:18 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1709242325-17218-23-git-send-email-roretzla@linux.microsoft.com>
2024-02-29 21:13 ` |SUCCESS| pw137549-137564 [PATCH v5 22/22] devtools: forbid use argument variadic pack extension qemudev
2024-02-29 21:17 ` qemudev
2024-02-29 21:34 ` |SUCCESS| pw137564 " checkpatch
2024-02-29 22:24 ` 0-day Robot
2024-02-29 23:58 ` |SUCCESS| pw137549-137564 [PATCH] [v5,22/22] devtools: forbid use ar dpdklab
2024-03-01 0:04 ` dpdklab
2024-03-01 0:05 ` dpdklab
2024-03-01 0:10 ` dpdklab
2024-03-01 0:33 ` dpdklab
2024-03-01 0:34 ` dpdklab
2024-03-01 0:35 ` dpdklab
2024-03-01 0:38 ` dpdklab
2024-03-01 0:38 ` dpdklab
2024-03-01 0:39 ` dpdklab
2024-03-01 0:39 ` dpdklab
2024-03-01 0:41 ` dpdklab
2024-03-01 0:44 ` dpdklab
2024-03-01 0:45 ` dpdklab
2024-03-01 0:46 ` dpdklab
2024-03-01 0:46 ` dpdklab
2024-03-01 0:47 ` dpdklab
2024-03-01 4:08 ` dpdklab
2024-03-01 4:16 ` dpdklab
2024-03-01 4:18 ` dpdklab
2024-03-01 4:20 ` dpdklab
2024-03-01 4:21 ` dpdklab
2024-03-01 4:21 ` dpdklab
2024-03-01 4:22 ` dpdklab
2024-03-01 4:31 ` dpdklab
2024-03-01 4:32 ` dpdklab
2024-03-01 4:33 ` dpdklab
2024-03-01 4:34 ` dpdklab
2024-03-01 4:34 ` dpdklab
2024-03-01 4:34 ` dpdklab
2024-03-01 4:35 ` dpdklab
2024-03-01 4:35 ` dpdklab
2024-03-01 4:36 ` dpdklab
2024-03-01 4:36 ` dpdklab
2024-03-01 4:36 ` dpdklab
2024-03-01 4:36 ` dpdklab
2024-03-01 4:37 ` dpdklab
2024-03-01 4:37 ` dpdklab
2024-03-01 4:37 ` dpdklab
2024-03-01 4:37 ` dpdklab
2024-03-01 4:37 ` dpdklab
2024-03-01 4:38 ` dpdklab
2024-03-01 4:38 ` dpdklab
2024-03-01 4:39 ` dpdklab
2024-03-01 4:39 ` dpdklab
2024-03-01 4:39 ` dpdklab
2024-03-01 4:39 ` dpdklab
2024-03-01 4:40 ` dpdklab
2024-03-01 4:44 ` dpdklab
2024-03-01 4:45 ` dpdklab
2024-03-01 4:46 ` dpdklab
2024-03-01 4:46 ` dpdklab
2024-03-01 4:46 ` dpdklab
2024-03-01 4:47 ` dpdklab
2024-03-01 4:47 ` dpdklab
2024-03-01 4:54 ` dpdklab
2024-03-01 4:54 ` dpdklab
2024-03-01 5:08 ` dpdklab
2024-03-01 5:16 ` dpdklab
2024-03-01 5:20 ` dpdklab
2024-03-01 6:05 ` dpdklab
2024-03-01 7:04 ` dpdklab
2024-03-01 9:17 ` dpdklab
2024-03-01 14:47 ` dpdklab
2024-03-01 14:52 ` dpdklab
2024-03-01 15:00 ` dpdklab
2024-03-01 15:07 ` dpdklab
2024-03-02 14:26 ` |WARNING| " dpdklab
2024-03-04 10:11 ` |SUCCESS| " dpdklab
2024-03-04 10:37 ` dpdklab
2024-03-04 11:17 ` dpdklab [this message]
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=65e5ade6.250a0220.47bd2.0cabSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=roretzla@linux.microsoft.com \
--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).