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] f2eea2f37a82bb73fb01d56350708f7d70e21379
Date: Thu, 26 Dec 2024 22:35:04 -0800 (PST)	[thread overview]
Message-ID: <676e4a98.050a0220.56a56.2460SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing pending_

Branch: tags/v24.11

f2eea2f37a82bb73fb01d56350708f7d70e21379 --> testing pending

Upstream job id: Generic-DPDK-Compile-Meson#347009

Test environment and result as below:

+------------------------------------+--------------------+
|            Environment             | dpdk_meson_compile |
+====================================+====================+
| Ubuntu 20.04 ARM GCC Cross Compile | PEND               |
+------------------------------------+--------------------+
| RHEL9 (ARM)                        | PEND               |
+------------------------------------+--------------------+
| Debian 12 with MUSDK               | PASS               |
+------------------------------------+--------------------+
| Fedora 40 (ARM)                    | PEND               |
+------------------------------------+--------------------+
| Fedora 41 (ARM)                    | PEND               |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE               | PEND               |
+------------------------------------+--------------------+
| Fedora 40 (ARM Clang)              | PEND               |
+------------------------------------+--------------------+
| Debian 11 (Buster) (ARM)           | PEND               |
+------------------------------------+--------------------+


Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: Depends on container host
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

RHEL9 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)

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

Fedora 40 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)

Fedora 41 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)

Ubuntu 20.04 ARM SVE
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0

Fedora 40 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.8 (Fedora 18.1.8-1.fc40)

Debian 11 (Buster) (ARM)
	Kernel: Depends on container host
	Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-12-27  6:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-27  6:35 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-27  5:59 dpdklab
2024-12-27  5:40 dpdklab
2024-12-27  5:16 dpdklab
2024-12-26  7:45 dpdklab
2024-12-26  7:22 dpdklab
2024-12-26  6:52 dpdklab
2024-12-26  5:16 dpdklab
2024-12-25  5:28 dpdklab
2024-12-25  5:26 dpdklab
2024-12-25  5:17 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=676e4a98.050a0220.56a56.2460SMTPIN_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).