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] c66daa12e76d7b4912cfb7109a761856a7a873ab
Date: Thu, 19 Dec 2024 22:25:52 -0800 (PST)	[thread overview]
Message-ID: <67650df0.050a0220.1ce9ce.b2b0SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing pending_

Branch: tags/v23.11

c66daa12e76d7b4912cfb7109a761856a7a873ab --> testing pending

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

Test environment and result as below:

+-----------------------+--------------+------------------------------+---------------------------+----------------+
|      Environment      | lpm_autotest | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest | dpdk_unit_test |
+=======================+==============+==============================+===========================+================+
| Ubuntu 20.04 ARM SVE  | PEND         | SKIPPED                      | SKIPPED                   | SKIPPED        |
+-----------------------+--------------+------------------------------+---------------------------+----------------+
| Debian 12 (arm)       | SKIPPED      | PEND                         | PASS                      | PEND           |
+-----------------------+--------------+------------------------------+---------------------------+----------------+
| CentOS Stream 9 (ARM) | SKIPPED      | SKIPPED                      | SKIPPED                   | PEND           |
+-----------------------+--------------+------------------------------+---------------------------+----------------+
| Fedora 39 (ARM)       | SKIPPED      | SKIPPED                      | SKIPPED                   | PEND           |
+-----------------------+--------------+------------------------------+---------------------------+----------------+
| Fedora 39 (ARM Clang) | SKIPPED      | SKIPPED                      | SKIPPED                   | PEND           |
+-----------------------+--------------+------------------------------+---------------------------+----------------+
| Fedora 40 (ARM)       | SKIPPED      | SKIPPED                      | SKIPPED                   | PEND           |
+-----------------------+--------------+------------------------------+---------------------------+----------------+
| Ubuntu 22.04 (ARM)    | SKIPPED      | SKIPPED                      | SKIPPED                   | PEND           |
+-----------------------+--------------+------------------------------+---------------------------+----------------+
| RHEL9 (ARM)           | SKIPPED      | SKIPPED                      | SKIPPED                   | PEND           |
+-----------------------+--------------+------------------------------+---------------------------+----------------+
| Ubuntu 24.04 (ARM)    | SKIPPED      | SKIPPED                      | SKIPPED                   | PEND           |
+-----------------------+--------------+------------------------------+---------------------------+----------------+
| Fedora 40 (ARM Clang) | SKIPPED      | SKIPPED                      | SKIPPED                   | PEND           |
+-----------------------+--------------+------------------------------+---------------------------+----------------+
| Ubuntu 20.04 (ARM)    | SKIPPED      | SKIPPED                      | SKIPPED                   | PEND           |
+-----------------------+--------------+------------------------------+---------------------------+----------------+


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

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

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

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

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

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

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

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

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-12-20  6:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20  6:25 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-21  6:05 dpdklab
2024-12-21  5:35 dpdklab
2024-12-21  5:17 dpdklab
2024-12-20  6:50 dpdklab
2024-12-20  6:47 dpdklab
2024-12-20  6:01 dpdklab
2024-12-19  7:12 dpdklab
2024-12-19  6:57 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=67650df0.050a0220.1ce9ce.b2b0SMTPIN_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).