automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] ff4d4839f9c2a6d05dca0a25ed6b1549402e1682
Date: Thu, 12 Sep 2024 06:29:25 -0700 (PDT)	[thread overview]
Message-ID: <66e2ecb5.050a0220.15b29a.5ec0SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing pending_

Branch: tags/v22.11

ff4d4839f9c2a6d05dca0a25ed6b1549402e1682 --> testing pending

Upstream job id: Generic-VM-Unit-Test-DPDK#25223

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           |
+---------------------+----------------+
| Fedora 38           | PEND           |
+---------------------+----------------+
| Fedora 39           | PEND           |
+---------------------+----------------+
| Fedora 40 (Clang)   | PEND           |
+---------------------+----------------+
| Fedora 39 (Clang)   | PEND           |
+---------------------+----------------+
| Fedora 40           | PEND           |
+---------------------+----------------+
| RHEL 7              | PEND           |
+---------------------+----------------+
| RHEL9               | PEND           |
+---------------------+----------------+
| RHEL8               | PEND           |
+---------------------+----------------+
| Ubuntu 20.04        | PEND           |
+---------------------+----------------+
| Ubuntu 22.04        | PEND           |
+---------------------+----------------+
| Ubuntu 24.04        | 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)

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1 20240316 (Red Hat 13.2.1-7)

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)

Fedora 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)

RHEL 7
	Kernel: Depends on container host
	Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

RHEL8
	Kernel: Depends on container host
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)

Ubuntu 20.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Ubuntu 22.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 24.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/30576/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2024-09-12 13:29 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 13:29 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-18  9:39 dpdklab
2024-09-18  7:35 dpdklab
2024-09-18  7:25 dpdklab
2024-09-18  7:23 dpdklab
2024-09-17  6:52 dpdklab
2024-09-17  6:44 dpdklab
2024-09-16  6:28 dpdklab
2024-09-16  5:40 dpdklab
2024-09-16  5:08 dpdklab
2024-09-15  5:37 dpdklab
2024-09-15  5:32 dpdklab
2024-09-15  4:58 dpdklab
2024-09-14  5:47 dpdklab
2024-09-14  5:46 dpdklab
2024-09-14  5:38 dpdklab
2024-09-14  5:34 dpdklab
2024-09-13  6:50 dpdklab
2024-09-13  5:48 dpdklab
2024-09-13  5:13 dpdklab
2024-09-13  4:46 dpdklab
2024-09-12 14:12 dpdklab
2024-09-12 13:57 dpdklab
2024-09-12 13:12 dpdklab
2024-09-11 13:22 dpdklab
2024-09-11  7:32 dpdklab
2024-09-11  7:23 dpdklab
2024-09-11  6:46 dpdklab
2024-09-10 14:32 dpdklab
2024-09-10 12:41 dpdklab
2024-09-10 12:22 dpdklab
2024-09-10 12:12 dpdklab
2024-09-10  6:38 dpdklab
2024-09-09  5:08 dpdklab
2024-09-09  4:41 dpdklab
2024-09-09  4:34 dpdklab
2024-09-09  4:33 dpdklab
2024-09-08  7:31 dpdklab
2024-09-08  5:21 dpdklab
2024-09-08  4:59 dpdklab
2024-09-08  4:50 dpdklab
2024-09-08  4:49 dpdklab
2024-09-07 10:56 dpdklab
2024-09-07 10:05 dpdklab
2024-09-07  5:12 dpdklab
2024-09-06 10:57 dpdklab
2024-09-05  9:33 dpdklab
2024-09-04  7:20 dpdklab
2024-09-03  7:15 dpdklab
2024-09-02  7:54 dpdklab
2024-09-01  7:21 dpdklab
2024-08-31  4:42 dpdklab
2024-08-30  6:53 dpdklab
2024-08-28  8:04 dpdklab
2024-08-28  7:48 dpdklab
2024-08-27  6:58 dpdklab
2024-08-26  9:34 dpdklab
2024-08-26  7:05 dpdklab
2024-08-25  8:58 dpdklab
2024-08-25  7:55 dpdklab
2024-08-24 11:02 dpdklab
2024-08-24 10:46 dpdklab
2024-08-23  7:15 dpdklab
2024-08-23  4:50 dpdklab
2024-08-22  7:14 dpdklab
2024-08-21  7:44 dpdklab
2024-08-21  7:08 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=66e2ecb5.050a0220.15b29a.5ec0SMTPIN_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).