From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw151219-151228 [PATCH] [RFC,v2,10/10] eal: deprecate weak
Date: Sun, 09 Feb 2025 11:42:24 -0800 (PST) [thread overview]
Message-ID: <67a90520.050a0220.6e6cd.2a61SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250209172850.2429075-11-david.marchand@redhat.com>
Test-Label: iol-sample-apps-testing
Test-Status: WARNING
http://dpdk.org/patch/151228
_Testing issues_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Sunday, February 09 2025 17:28:48
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3553897d84d8b54a1b1136cbf04dd7f1a40fd85b
151219-151228 --> testing issues
Upstream job id: ACVP-FIPS-testing#8854
Test environment and result as below:
+--------------------+----------------------+----------------------+
| Environment | compressdev_zlib_pmd | dpdk_fips_validation |
+====================+======================+======================+
| Ubuntu 22.04 (ARM) | PASS | SKIPPED |
+--------------------+----------------------+----------------------+
| Ubuntu 22.04 | PASS | SKIPPED |
+--------------------+----------------------+----------------------+
| Ubuntu 20.04 | SKIPPED | WARN |
+--------------------+----------------------+----------------------+
==== 20 line log output for Ubuntu 20.04 (dpdk_fips_validation): ====
INFO:root:Downloading verdict for vector set 2880561
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Done
INFO:root:Using response file...
INFO:root:Uploading response file...
INFO:root:Fetching verdict...
INFO:root:Downloading verdict for vector set 2880562
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Done
INFO:root:Using response file...
INFO:root:Uploading response file...
INFO:root:Fetching verdict...
INFO:root:Downloading verdict for vector set 2880563
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Done
==== End log output ====
Ubuntu 22.04 (ARM)
Kernel: 5.15.0-97-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 20.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32541/
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:[~2025-02-09 19:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250209172850.2429075-11-david.marchand@redhat.com>
2025-02-09 17:07 ` |SUCCESS| pw151219-151228 [RFC v2 10/10] eal: deprecate weak symbols qemudev
2025-02-09 17:12 ` qemudev
2025-02-09 18:11 ` |SUCCESS| pw151219-151228 [PATCH] [RFC,v2,10/10] eal: deprecate weak dpdklab
2025-02-09 18:21 ` |PENDING| " dpdklab
2025-02-09 18:23 ` |SUCCESS| " dpdklab
2025-02-09 18:27 ` |SUCCESS| pw151228 [RFC v2 10/10] eal: deprecate weak symbols 0-day Robot
2025-02-09 18:28 ` |SUCCESS| pw151219-151228 [PATCH] [RFC,v2,10/10] eal: deprecate weak dpdklab
2025-02-09 18:29 ` |PENDING| " dpdklab
2025-02-09 18:31 ` dpdklab
2025-02-09 18:35 ` |SUCCESS| " dpdklab
2025-02-09 18:35 ` dpdklab
2025-02-09 18:41 ` dpdklab
2025-02-09 18:45 ` dpdklab
2025-02-09 18:49 ` |PENDING| " dpdklab
2025-02-09 19:02 ` |SUCCESS| " dpdklab
2025-02-09 19:16 ` dpdklab
2025-02-09 19:16 ` dpdklab
2025-02-09 19:16 ` dpdklab
2025-02-09 19:42 ` dpdklab [this message]
2025-02-09 20:29 ` dpdklab
2025-02-09 20:37 ` dpdklab
2025-02-09 23:58 ` 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=67a90520.050a0220.6e6cd.2a61SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@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).