From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] d20fd65f258afb5b572fe686b7d1032aeb95e079
Date: Sun, 06 Oct 2024 22:28:50 -0700 (PDT) [thread overview]
Message-ID: <67037192.4a0a0220.22775e.622eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: tags/v21.11
d20fd65f258afb5b572fe686b7d1032aeb95e079 --> testing pending
Upstream job id: Generic-VM-Unit-Test-DPDK#25535
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2022 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PEND |
+---------------------+----------------+
| Debian Bullseye | PEND |
+---------------------+----------------+
| Fedora 37 | PEND |
+---------------------+----------------+
| Fedora 38 | PEND |
+---------------------+----------------+
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
Debian Bullseye
Kernel: Depends on container host
Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1 20230508 (Red Hat 12.3.1-1)
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1 20240316 (Red Hat 13.2.1-7)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/30889/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-10-07 5:28 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 5:28 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-07 6:20 dpdklab
2024-10-07 5:16 dpdklab
2024-10-07 5:12 dpdklab
2024-10-07 5:12 dpdklab
2024-10-06 8:26 dpdklab
2024-10-06 6:05 dpdklab
2024-10-06 5:08 dpdklab
2024-10-05 6:23 dpdklab
2024-10-05 6:19 dpdklab
2024-10-05 6:04 dpdklab
2024-10-05 5:20 dpdklab
2024-10-04 11:34 dpdklab
2024-10-04 8:30 dpdklab
2024-10-04 7:56 dpdklab
2024-10-04 7:39 dpdklab
2024-10-04 6:38 dpdklab
2024-10-03 6:08 dpdklab
2024-10-03 5:49 dpdklab
2024-10-03 5:14 dpdklab
2024-10-01 7:41 dpdklab
2024-10-01 6:26 dpdklab
2024-10-01 5:35 dpdklab
2024-10-01 5:22 dpdklab
2024-09-30 7:35 dpdklab
2024-09-30 5:57 dpdklab
2024-09-30 5:50 dpdklab
2024-09-30 5:32 dpdklab
2024-09-30 5:10 dpdklab
2024-09-29 5:37 dpdklab
2024-09-29 4:53 dpdklab
2024-09-29 4:50 dpdklab
2024-09-28 6:00 dpdklab
2024-09-28 5:45 dpdklab
2024-09-28 5:37 dpdklab
2024-09-28 4:17 dpdklab
2024-09-27 10:24 dpdklab
2024-09-27 8:33 dpdklab
2024-09-27 6:42 dpdklab
2024-09-26 11:43 dpdklab
2024-09-26 11:00 dpdklab
2024-09-26 10:47 dpdklab
2024-09-26 7:56 dpdklab
2024-09-26 6:23 dpdklab
2024-09-25 6:29 dpdklab
2024-09-25 5:53 dpdklab
2024-09-25 5:04 dpdklab
2024-09-24 6:21 dpdklab
2024-09-24 5:43 dpdklab
2024-09-24 5:30 dpdklab
2024-09-24 4:20 dpdklab
2024-09-23 8:15 dpdklab
2024-09-23 5:41 dpdklab
2024-09-23 5:26 dpdklab
2024-09-23 4:44 dpdklab
2024-09-22 5:48 dpdklab
2024-09-22 5:38 dpdklab
2024-09-22 5:29 dpdklab
2024-09-22 4:55 dpdklab
2024-09-21 5:49 dpdklab
2024-09-21 5:43 dpdklab
2024-09-21 4:43 dpdklab
2024-09-20 7:11 dpdklab
2024-09-20 6:22 dpdklab
2024-09-20 6:04 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=67037192.4a0a0220.22775e.622eSMTPIN_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).