From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] f2eea2f37a82bb73fb01d56350708f7d70e21379
Date: Thu, 30 Jan 2025 22:01:14 -0800 (PST) [thread overview]
Message-ID: <679c672a.170a0220.15a9b7.c70eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: tags/v24.11
f2eea2f37a82bb73fb01d56350708f7d70e21379 --> testing pending
Upstream job id: Template-DTS-Pipeline#210009
Test environment and result as below:
+--------------------+----------------------+----------------------+
| Environment | dpdk_fips_validation | compressdev_zlib_pmd |
+====================+======================+======================+
| Ubuntu 20.04 | PEND | SKIPPED |
+--------------------+----------------------+----------------------+
| Ubuntu 22.04 (ARM) | SKIPPED | PASS |
+--------------------+----------------------+----------------------+
Ubuntu 20.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Ubuntu 22.04 (ARM)
Kernel: 5.15.0-97-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/32399/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-01-31 6:01 UTC|newest]
Thread overview: 122+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 6:01 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-31 8:54 dpdklab
2025-01-31 6:23 dpdklab
2025-01-31 6:14 dpdklab
2025-01-31 5:53 dpdklab
2025-01-30 6:06 dpdklab
2025-01-30 5:49 dpdklab
2025-01-30 5:35 dpdklab
2025-01-29 6:04 dpdklab
2025-01-29 5:50 dpdklab
2025-01-29 5:33 dpdklab
2025-01-28 6:39 dpdklab
2025-01-28 6:25 dpdklab
2025-01-28 6:18 dpdklab
2025-01-28 5:41 dpdklab
2025-01-27 6:48 dpdklab
2025-01-27 6:21 dpdklab
2025-01-27 5:49 dpdklab
2025-01-27 5:20 dpdklab
2025-01-26 5:57 dpdklab
2025-01-26 5:41 dpdklab
2025-01-26 5:39 dpdklab
2025-01-25 9:31 dpdklab
2025-01-25 8:20 dpdklab
2025-01-25 7:14 dpdklab
2025-01-25 6:55 dpdklab
2025-01-24 5:47 dpdklab
2025-01-23 6:00 dpdklab
2025-01-23 5:54 dpdklab
2025-01-23 5:33 dpdklab
2025-01-22 7:15 dpdklab
2025-01-22 6:39 dpdklab
2025-01-22 6:12 dpdklab
2025-01-21 6:23 dpdklab
2025-01-21 6:02 dpdklab
2025-01-20 7:01 dpdklab
2025-01-20 6:20 dpdklab
2025-01-20 6:11 dpdklab
2025-01-20 5:35 dpdklab
2025-01-19 7:09 dpdklab
2025-01-19 6:39 dpdklab
2025-01-19 6:08 dpdklab
2025-01-19 6:06 dpdklab
2025-01-19 5:14 dpdklab
2025-01-18 5:59 dpdklab
2025-01-18 5:54 dpdklab
2025-01-18 5:49 dpdklab
2025-01-18 5:40 dpdklab
2025-01-18 5:30 dpdklab
2025-01-17 5:23 dpdklab
2025-01-17 5:13 dpdklab
2025-01-16 5:49 dpdklab
2025-01-16 5:49 dpdklab
2025-01-16 5:30 dpdklab
2025-01-16 5:26 dpdklab
2025-01-15 6:40 dpdklab
2025-01-15 6:15 dpdklab
2025-01-15 5:55 dpdklab
2025-01-15 5:51 dpdklab
2025-01-14 6:12 dpdklab
2025-01-14 6:10 dpdklab
2025-01-14 5:51 dpdklab
2025-01-14 5:29 dpdklab
2025-01-13 5:49 dpdklab
2025-01-13 5:46 dpdklab
2025-01-13 5:43 dpdklab
2025-01-13 5:14 dpdklab
2025-01-12 7:08 dpdklab
2025-01-12 6:16 dpdklab
2025-01-12 6:08 dpdklab
2025-01-12 5:13 dpdklab
2025-01-11 5:31 dpdklab
2025-01-11 5:29 dpdklab
2025-01-11 5:24 dpdklab
2025-01-10 7:04 dpdklab
2025-01-10 6:56 dpdklab
2025-01-10 5:59 dpdklab
2025-01-10 5:40 dpdklab
2025-01-09 11:01 dpdklab
2025-01-09 9:20 dpdklab
2025-01-09 7:54 dpdklab
2025-01-09 3:25 dpdklab
2025-01-07 10:07 dpdklab
2025-01-07 8:32 dpdklab
2025-01-06 7:39 dpdklab
2025-01-06 7:27 dpdklab
2025-01-06 6:17 dpdklab
2025-01-06 5:52 dpdklab
2025-01-05 7:31 dpdklab
2025-01-05 7:19 dpdklab
2025-01-05 6:59 dpdklab
2025-01-05 6:42 dpdklab
2025-01-05 6:02 dpdklab
2025-01-04 6:11 dpdklab
2025-01-04 5:44 dpdklab
2025-01-04 5:34 dpdklab
2025-01-04 5:30 dpdklab
2025-01-03 7:17 dpdklab
2025-01-03 6:33 dpdklab
2024-12-31 5:55 dpdklab
2024-12-31 5:42 dpdklab
2024-12-31 5:16 dpdklab
2024-12-30 5:53 dpdklab
2024-12-30 5:43 dpdklab
2024-12-30 5:40 dpdklab
2024-12-29 6:47 dpdklab
2024-12-29 5:49 dpdklab
2024-12-29 5:14 dpdklab
2024-12-28 6:35 dpdklab
2024-12-28 6:14 dpdklab
2024-12-28 6:10 dpdklab
2024-12-27 6:35 dpdklab
2024-12-27 5:59 dpdklab
2024-12-27 5:40 dpdklab
2024-12-27 5:16 dpdklab
2024-12-26 7:45 dpdklab
2024-12-26 7:22 dpdklab
2024-12-26 6:52 dpdklab
2024-12-26 5:16 dpdklab
2024-12-25 5:28 dpdklab
2024-12-25 5:26 dpdklab
2024-12-25 5:17 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=679c672a.170a0220.15a9b7.c70eSMTPIN_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).