From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] 39b54f2dcf44ad1f91eabc7080cd5dea763607fd
Date: Wed, 29 Oct 2025 17:23:17 -0700 (PDT) [thread overview]
Message-ID: <6902aff5.050a0220.35612f.8060SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: dpdk
39b54f2dcf44ad1f91eabc7080cd5dea763607fd --> testing pending
Upstream job id: Template-DTS-Pipeline#252050
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/35394/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-10-30 0:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 0:23 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-30 0:26 dpdklab
2025-10-30 0:20 dpdklab
2025-10-30 0:12 dpdklab
2025-10-30 0:11 dpdklab
2025-10-28 23:45 dpdklab
2025-10-28 23:09 dpdklab
2025-10-28 19:46 dpdklab
2025-10-28 19:16 dpdklab
2025-10-27 19:28 dpdklab
2025-10-27 19:20 dpdklab
2025-10-27 19:19 dpdklab
2025-10-27 19:18 dpdklab
2025-10-27 19:17 dpdklab
2025-10-26 4:56 dpdklab
2025-10-26 0:36 dpdklab
2025-10-26 0:22 dpdklab
2025-10-26 0:16 dpdklab
2025-10-26 0:10 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=6902aff5.050a0220.35612f.8060SMTPIN_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).