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] 47768aac18d7d90d7df29d9d25bbc362c7b4da60
Date: Tue, 02 Jul 2024 09:14:39 -0700 (PDT)	[thread overview]
Message-ID: <6684276f.050a0220.71cc.f491SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing pending_

Branch: dpdk-next-net-intel

47768aac18d7d90d7df29d9d25bbc362c7b4da60 --> testing pending

Test environment and result as below:

+-------------------+----------------+
|    Environment    | dpdk_unit_test |
+===================+================+
| CentOS Stream 8   | PASS           |
+-------------------+----------------+
| CentOS Stream 9   | PASS           |
+-------------------+----------------+
| Debian Bullseye   | PASS           |
+-------------------+----------------+
| Debian 12         | PASS           |
+-------------------+----------------+
| Fedora 37         | PASS           |
+-------------------+----------------+
| Fedora 38         | PASS           |
+-------------------+----------------+
| Fedora 38 (Clang) | PASS           |
+-------------------+----------------+
| Fedora 39         | PASS           |
+-------------------+----------------+
| Fedora 39 (Clang) | PASS           |
+-------------------+----------------+
| Fedora 40         | PEND           |
+-------------------+----------------+
| Fedora 40 (Clang) | PEND           |
+-------------------+----------------+
| openSUSE Leap 15  | PASS           |
+-------------------+----------------+
| RHEL8             | PEND           |
+-------------------+----------------+
| RHEL9             | PEND           |
+-------------------+----------------+
| Ubuntu 20.04      | PEND           |
+-------------------+----------------+
| Ubuntu 24.04      | PEND           |
+-------------------+----------------+
| Ubuntu 22.04      | PEND           |
+-------------------+----------------+


CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 38 (Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.1.1

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

Ubuntu 20.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

Ubuntu 24.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.2.0

Ubuntu 22.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-07-02 16:14 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-02 16:14 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-02 21:52 dpdklab
2024-07-02 21:52 dpdklab
2024-07-02 21:51 dpdklab
2024-07-02 21:44 dpdklab
2024-07-02 21:42 dpdklab
2024-07-02 21:32 dpdklab
2024-07-02 21:24 dpdklab
2024-07-02 21:17 dpdklab
2024-07-02 21:10 dpdklab
2024-07-02 20:56 dpdklab
2024-07-02 20:48 dpdklab
2024-07-02 20:42 dpdklab
2024-07-02 20:41 dpdklab
2024-07-02 20:33 dpdklab
2024-07-02 20:32 dpdklab
2024-07-02 19:35 dpdklab
2024-07-02 19:28 dpdklab
2024-07-02 19:03 dpdklab
2024-07-02 19:01 dpdklab
2024-07-02 19:00 dpdklab
2024-07-02 18:57 dpdklab
2024-07-02 18:54 dpdklab
2024-07-02 18:51 dpdklab
2024-07-02 18:16 dpdklab
2024-07-02 18:09 dpdklab
2024-07-02 18:04 dpdklab
2024-07-02 18:03 dpdklab
2024-07-02 17:59 dpdklab
2024-07-02 17:57 dpdklab
2024-07-02 17:53 dpdklab
2024-07-02 17:52 dpdklab
2024-07-02 17:35 dpdklab
2024-07-02 17:35 dpdklab
2024-07-02 17:34 dpdklab
2024-07-02 17:29 dpdklab
2024-07-02 17:28 dpdklab
2024-07-02 17:25 dpdklab
2024-07-02 17:25 dpdklab
2024-07-02 17:25 dpdklab
2024-07-02 17:25 dpdklab
2024-07-02 17:23 dpdklab
2024-07-02 17:20 dpdklab
2024-07-02 17:19 dpdklab
2024-07-02 17:18 dpdklab
2024-07-02 17:18 dpdklab
2024-07-02 17:14 dpdklab
2024-07-02 17:10 dpdklab
2024-07-02 17:10 dpdklab
2024-07-02 17:09 dpdklab
2024-07-02 17:07 dpdklab
2024-07-02 16:41 dpdklab
2024-07-02 16:27 dpdklab
2024-07-02 16:25 dpdklab
2024-07-02 16:23 dpdklab
2024-07-02 16:21 dpdklab
2024-07-02 16:19 dpdklab
2024-07-02 16:17 dpdklab
2024-07-02 16:08 dpdklab
2024-07-02 16:03 dpdklab
2024-07-02 16:01 dpdklab
2024-07-02 15:59 dpdklab
2024-07-02 15:48 dpdklab
2024-07-02 15:48 dpdklab
2024-07-02 15:43 dpdklab
2024-07-02 15:42 dpdklab
2024-07-02 15:28 dpdklab
2024-07-02 14:20 dpdklab
2024-07-02 14:03 dpdklab
2024-07-02 14:02 dpdklab
2024-07-02 13:58 dpdklab
2024-07-02 13:58 dpdklab
2024-07-02 13:58 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=6684276f.050a0220.71cc.f491SMTPIN_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).