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,
	Nithin Dabilpuram <ndabilpuram@marvell.com>
Subject: |FAILURE| pw152750-152753 [PATCH] [RFC,4/4] net/cnxk: report link ty
Date: Thu, 03 Apr 2025 05:59:17 -0700 (PDT)	[thread overview]
Message-ID: <67ee8625.050a0220.240518.1fbfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250403070837.926292-4-ndabilpuram@marvell.com>

Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/152753

_Testing issues_

Submitter: Nithin Dabilpuram <ndabilpuram@marvell.com>
Date: Thursday, April 03 2025 07:08:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b40c403777e93242a377c07ff51964480d40b51d

152750-152753 --> testing issues

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

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9     | FAIL           |
+---------------------+----------------+
| CentOS Stream 10    | FAIL           |
+---------------------+----------------+
| Fedora 40           | FAIL           |
+---------------------+----------------+
| Debian 12           | FAIL           |
+---------------------+----------------+
| Fedora 40 (Clang)   | FAIL           |
+---------------------+----------------+
| Fedora 41 (Clang)   | FAIL           |
+---------------------+----------------+
| Fedora 41           | FAIL           |
+---------------------+----------------+
| RHEL9               | FAIL           |
+---------------------+----------------+
| RHEL8               | FAIL           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+
| Ubuntu 24.04        | FAIL           |
+---------------------+----------------+
| Ubuntu 22.04        | FAIL           |
+---------------------+----------------+
| Windows Server 2022 | FAIL           |
+---------------------+----------------+

==== Unit test summary for Windows Server 2022 (dpdk_unit_test): ====
Failed to get the unit test results.
Displaying the unit test results is not supported for some environments,
such as our aarch32 testing, where meson is not used to run the tests.
Download the logs available on our CI site.
==== End log output ====

CentOS Stream 9
	Kernel: Depends on container host
	Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)

CentOS Stream 10
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20241104 (Red Hat 14.2.1-6)

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

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

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

Fedora 41 (Clang)
	Kernel: Depends on container host
	Compiler: clang 19.1.5 (Fedora 19.1.5-1.fc41)

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

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

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 24.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

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

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32939/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-04-03 12:59 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250403070837.926292-4-ndabilpuram@marvell.com>
2025-04-03  6:35 ` |SUCCESS| pw152750-152753 [RFC PATCH 4/4] net/cnxk: report link type along with link status qemudev
2025-04-03  6:41 ` |FAILURE| " qemudev
2025-04-03  7:09 ` |SUCCESS| pw152753 " checkpatch
2025-04-03  8:02 ` |FAILURE| " 0-day Robot
2025-04-03  8:33 ` |SUCCESS| pw152750-152753 [PATCH] [RFC,4/4] net/cnxk: report link ty dpdklab
2025-04-03  8:39 ` dpdklab
2025-04-03  8:41 ` dpdklab
2025-04-03  8:55 ` dpdklab
2025-04-03  9:01 ` dpdklab
2025-04-03  9:03 ` dpdklab
2025-04-03  9:26 ` dpdklab
2025-04-03  9:37 ` |PENDING| " dpdklab
2025-04-03  9:48 ` |FAILURE| " dpdklab
2025-04-03  9:52 ` dpdklab
2025-04-03  9:53 ` dpdklab
2025-04-03  9:53 ` dpdklab
2025-04-03  9:58 ` dpdklab
2025-04-03 10:18 ` |PENDING| " dpdklab
2025-04-03 10:41 ` |FAILURE| " dpdklab
2025-04-03 10:50 ` |WARNING| " dpdklab
2025-04-03 11:41 ` |FAILURE| " dpdklab
2025-04-03 11:53 ` |SUCCESS| " dpdklab
2025-04-03 12:12 ` |FAILURE| " dpdklab
2025-04-03 12:59 ` dpdklab [this message]
2025-04-03 13:29 ` |SUCCESS| " dpdklab
2025-04-03 15:53 ` dpdklab
2025-04-03 19:32 ` dpdklab
2025-04-04  0:15 ` dpdklab
2025-04-04  0:41 ` dpdklab
2025-04-04 16:43 ` 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=67ee8625.050a0220.240518.1fbfSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ndabilpuram@marvell.com \
    --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).