From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, John McNamara <john.mcnamara@intel.com>
Subject: |WARNING| pw138952 [PATCH] [v1] doc: update release notes for 24.03
Date: Thu, 28 Mar 2024 06:09:40 -0700 (PDT) [thread overview]
Message-ID: <66056c14.050a0220.e164b.2d3aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240328120550.3573051-1-john.mcnamara@intel.com>
Test-Label: iol-sample-apps-testing
Test-Status: WARNING
http://dpdk.org/patch/138952
_Testing issues_
Submitter: John McNamara <john.mcnamara@intel.com>
Date: Thursday, March 28 2024 12:05:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c29202f2f70abd22e3d74e0671ec9f6cb9e387ee
138952 --> 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): ====
[2879/2892] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_memcpy_perf.c.o'.
[2880/2892] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_gcm.c.o'.
[2881/2892] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_ecdsa.c.o'.
[2882/2892] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_tdes.c.o'.
[2883/2892] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_ccm.c.o'.
[2884/2892] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_rsa.c.o'.
[2885/2892] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_table_combined.c.o'.
[2886/2892] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_dev_self_test.c.o'.
[2887/2892] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_main.c.o'.
[2888/2892] Linking target examples/dpdk-fips_validation.
[2889/2892] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_trace_perf.c.o'.
[2890/2892] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_ring_perf.c.o'.
[2891/2892] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_ring.c.o'.
[2892/2892] Linking target app/dpdk-test.
Processing file ../out/acvp-aes-cbc-vectors.json... Done
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...
==== End log output ====
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29673/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-28 13:09 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240328120550.3573051-1-john.mcnamara@intel.com>
2024-03-28 11:43 ` |SUCCESS| pw138952 [PATCH v1] " qemudev
2024-03-28 11:48 ` qemudev
2024-03-28 12:06 ` checkpatch
2024-03-28 12:47 ` |SUCCESS| pw138952 [PATCH] [v1] " dpdklab
2024-03-28 12:48 ` dpdklab
2024-03-28 12:48 ` dpdklab
2024-03-28 12:48 ` dpdklab
2024-03-28 12:49 ` dpdklab
2024-03-28 12:49 ` dpdklab
2024-03-28 12:49 ` dpdklab
2024-03-28 12:49 ` dpdklab
2024-03-28 12:49 ` dpdklab
2024-03-28 12:49 ` dpdklab
2024-03-28 12:50 ` dpdklab
2024-03-28 12:50 ` dpdklab
2024-03-28 12:50 ` dpdklab
2024-03-28 12:51 ` dpdklab
2024-03-28 12:51 ` dpdklab
2024-03-28 12:51 ` dpdklab
2024-03-28 12:51 ` dpdklab
2024-03-28 12:52 ` dpdklab
2024-03-28 12:52 ` dpdklab
2024-03-28 12:52 ` dpdklab
2024-03-28 12:52 ` dpdklab
2024-03-28 12:53 ` dpdklab
2024-03-28 12:54 ` dpdklab
2024-03-28 12:55 ` dpdklab
2024-03-28 12:55 ` dpdklab
2024-03-28 12:55 ` dpdklab
2024-03-28 12:56 ` dpdklab
2024-03-28 12:56 ` dpdklab
2024-03-28 12:57 ` dpdklab
2024-03-28 12:58 ` dpdklab
2024-03-28 12:58 ` dpdklab
2024-03-28 12:59 ` dpdklab
2024-03-28 12:59 ` dpdklab
2024-03-28 13:00 ` dpdklab
2024-03-28 13:00 ` dpdklab
2024-03-28 13:05 ` |SUCCESS| pw138952 [PATCH v1] " 0-day Robot
2024-03-28 13:06 ` |SUCCESS| pw138952 [PATCH] [v1] " dpdklab
2024-03-28 13:06 ` dpdklab
2024-03-28 13:06 ` dpdklab
2024-03-28 13:06 ` dpdklab
2024-03-28 13:07 ` dpdklab
2024-03-28 13:07 ` dpdklab
2024-03-28 13:07 ` dpdklab
2024-03-28 13:07 ` dpdklab
2024-03-28 13:08 ` dpdklab
2024-03-28 13:09 ` dpdklab
2024-03-28 13:09 ` dpdklab
2024-03-28 13:09 ` dpdklab [this message]
2024-03-28 13:09 ` dpdklab
2024-03-28 13:11 ` dpdklab
2024-03-28 13:11 ` dpdklab
2024-03-28 13:18 ` dpdklab
2024-03-28 13:20 ` dpdklab
2024-03-28 13:20 ` dpdklab
2024-03-28 13:20 ` dpdklab
2024-03-28 13:21 ` dpdklab
2024-03-28 13:22 ` dpdklab
2024-03-28 13:23 ` dpdklab
2024-03-28 13:28 ` dpdklab
2024-03-28 13:29 ` dpdklab
2024-03-28 13:30 ` dpdklab
2024-03-28 13:30 ` dpdklab
2024-03-28 13:30 ` dpdklab
2024-03-28 13:31 ` dpdklab
2024-03-28 13:31 ` dpdklab
2024-03-28 13:31 ` dpdklab
2024-03-28 13:32 ` dpdklab
2024-03-28 13:33 ` dpdklab
2024-03-28 13:36 ` dpdklab
2024-03-28 13:37 ` dpdklab
2024-03-28 13:38 ` dpdklab
2024-03-28 13:39 ` dpdklab
2024-03-28 13:39 ` dpdklab
2024-03-28 13:41 ` dpdklab
2024-03-28 13:42 ` dpdklab
2024-03-28 13:46 ` dpdklab
2024-03-28 13:52 ` dpdklab
2024-03-28 13:53 ` dpdklab
2024-03-28 13:54 ` dpdklab
2024-03-28 14:11 ` dpdklab
2024-04-02 14:54 ` dpdklab
2024-04-02 14:59 ` dpdklab
2024-04-02 15:02 ` dpdklab
2024-04-02 15:22 ` dpdklab
2024-04-02 15:26 ` 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=66056c14.050a0220.e164b.2d3aSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=john.mcnamara@intel.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).