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] a63c6426fdfd9233ba9c7d4503e52bff3732fe69
Date: Sat, 09 Nov 2024 17:32:37 -0800 (PST)	[thread overview]
Message-ID: <67300d35.050a0220.2a8256.29e5SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing pending_

Branch: dpdk

a63c6426fdfd9233ba9c7d4503e52bff3732fe69 --> testing pending

Upstream job id: Generic-Unit-Test-DPDK#289890

Test environment and result as below:

+-------------------+----------------+
|    Environment    | dpdk_unit_test |
+===================+================+
| Debian 12         | PEND           |
+-------------------+----------------+
| CentOS Stream 9   | PEND           |
+-------------------+----------------+
| Arch Linux        | PASS           |
+-------------------+----------------+
| Fedora 39         | PEND           |
+-------------------+----------------+
| Fedora 40 (Clang) | PEND           |
+-------------------+----------------+
| Fedora 39 (Clang) | PEND           |
+-------------------+----------------+
| Fedora 40         | PEND           |
+-------------------+----------------+
| RHEL9             | PEND           |
+-------------------+----------------+
| RHEL8             | PEND           |
+-------------------+----------------+
| Ubuntu 22.04      | PEND           |
+-------------------+----------------+
| Ubuntu 20.04      | PEND           |
+-------------------+----------------+
| Ubuntu 24.04      | PEND           |
+-------------------+----------------+


Debian 12
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

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

Arch Linux
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240805

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)

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 22.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 20.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.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/31493/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-11-10  1:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-10  1:32 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-10  1:47 dpdklab
2024-11-10  1:47 dpdklab
2024-11-10  1:29 dpdklab
2024-11-10  1:26 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=67300d35.050a0220.2a8256.29e5SMTPIN_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).