From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] 0bd935abcb823f581ce53986986aa54eaf6f8140
Date: Sat, 08 Nov 2025 21:16:31 -0800 (PST) [thread overview]
Message-ID: <691023af.170a0220.3043a3.f058SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: tags/v24.11
0bd935abcb823f581ce53986986aa54eaf6f8140 --> testing pending
Upstream job id: Template-DTS-Pipeline#253674
Test environment and result as below:
+--------------+----------------------+----------------------+
| Environment | dpdk_fips_validation | compressdev_zlib_pmd |
+==============+======================+======================+
| Ubuntu 20.04 | PEND | SKIPPED |
+--------------+----------------------+----------------------+
| Ubuntu 22.04 | SKIPPED | PASS |
+--------------+----------------------+----------------------+
Ubuntu 20.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/35512/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-11-09 5:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-09 5:16 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-09 6:40 dpdklab
2025-11-09 5:10 dpdklab
2025-11-09 5:10 dpdklab
2025-11-09 5:07 dpdklab
2025-11-08 6:10 dpdklab
2025-11-08 6:08 dpdklab
2025-11-08 5:10 dpdklab
2025-11-07 6:05 dpdklab
2025-11-07 5:47 dpdklab
2025-11-07 5:22 dpdklab
2025-11-07 5:15 dpdklab
2025-11-06 6:58 dpdklab
2025-11-06 6:03 dpdklab
2025-11-06 6:02 dpdklab
2025-11-06 5:11 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=691023af.170a0220.3043a3.f058SMTPIN_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).