From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] 680818068d31764357075cde440232ce5ab8b786
Date: Mon, 16 Sep 2024 23:33:02 -0700 (PDT) [thread overview]
Message-ID: <66e9229e.0c0a0220.35c7f3.e720SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: tags/v21.11
680818068d31764357075cde440232ce5ab8b786 --> testing pending
Upstream job id: Generic-VM-Unit-Test-DPDK#25265
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2022 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PEND |
+---------------------+----------------+
| Debian Bullseye | PEND |
+---------------------+----------------+
| Debian 12 | PEND |
+---------------------+----------------+
| Fedora 37 | PEND |
+---------------------+----------------+
| Fedora 38 (Clang) | 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
Debian 12
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1 20230508 (Red Hat 12.3.1-1)
Fedora 38 (Clang)
Kernel: Depends on container host
Compiler: clang 16.0.6 (Fedora 16.0.6-4.fc38)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/30618/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-09-17 6:33 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 6:33 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-19 15:02 dpdklab
2024-09-19 12:23 dpdklab
2024-09-19 11:46 dpdklab
2024-09-19 11:36 dpdklab
2024-09-19 10:12 dpdklab
2024-09-18 6:27 dpdklab
2024-09-18 6:21 dpdklab
2024-09-17 7:06 dpdklab
2024-09-16 5:02 dpdklab
2024-09-16 5:01 dpdklab
2024-09-16 4:53 dpdklab
2024-09-15 5:30 dpdklab
2024-09-15 5:02 dpdklab
2024-09-15 4:48 dpdklab
2024-09-15 4:44 dpdklab
2024-09-15 4:38 dpdklab
2024-09-14 7:31 dpdklab
2024-09-14 5:43 dpdklab
2024-09-14 5:35 dpdklab
2024-09-14 5:24 dpdklab
2024-09-13 8:49 dpdklab
2024-09-13 6:50 dpdklab
2024-09-13 6:30 dpdklab
2024-09-13 5:36 dpdklab
2024-09-13 5:23 dpdklab
2024-09-12 12:35 dpdklab
2024-09-12 11:57 dpdklab
2024-09-12 11:45 dpdklab
2024-09-11 13:47 dpdklab
2024-09-11 8:32 dpdklab
2024-09-11 8:00 dpdklab
2024-09-11 7:13 dpdklab
2024-09-11 7:04 dpdklab
2024-09-10 11:23 dpdklab
2024-09-10 10:11 dpdklab
2024-09-10 9:23 dpdklab
2024-09-10 5:27 dpdklab
2024-09-09 7:04 dpdklab
2024-09-09 5:53 dpdklab
2024-09-09 5:17 dpdklab
2024-09-09 5:10 dpdklab
2024-09-09 4:51 dpdklab
2024-09-08 5:23 dpdklab
2024-09-08 5:08 dpdklab
2024-09-08 4:37 dpdklab
2024-09-07 15:01 dpdklab
2024-09-07 10:15 dpdklab
2024-09-07 9:37 dpdklab
2024-09-07 7:43 dpdklab
2024-09-07 4:47 dpdklab
2024-09-06 22:11 dpdklab
2024-09-06 11:20 dpdklab
2024-09-06 11: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=66e9229e.0c0a0220.35c7f3.e720SMTPIN_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).