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,
	Wathsala Vithanage <wathsala.vithanage@arm.com>
Subject: |FAILURE| pw153504-153506 [PATCH] [RFC,v4,3/3] ethdev: introduce the
Date: Sat, 17 May 2025 09:56:22 -0700 (PDT)	[thread overview]
Message-ID: <6828bfb6.c80a0220.d652b.b4e1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250517151736.2565461-4-wathsala.vithanage@arm.com>

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

_Testing issues_

Submitter: Wathsala Vithanage <wathsala.vithanage@arm.com>
Date: Saturday, May 17 2025 15:17:35 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ff05ee3e3f8fb4ce958a2ce6461e8141aea959c6

153504-153506 --> testing issues

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

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 10    | PASS           |
+---------------------+----------------+
| Debian 12           | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+
| Fedora 40 (Clang)   | PASS           |
+---------------------+----------------+
| RHEL9               | PASS           |
+---------------------+----------------+
| Fedora 41 (Clang)   | PASS           |
+---------------------+----------------+
| Fedora 40           | PASS           |
+---------------------+----------------+
| Fedora 41           | PASS           |
+---------------------+----------------+
| Ubuntu 22.04        | PASS           |
+---------------------+----------------+
| Ubuntu 24.04        | PASS           |
+---------------------+----------------+
| RHEL8               | PASS           |
+---------------------+----------------+
| 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 10
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20241104 (Red Hat 14.2.1-6)

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.5.0 20240719 (Red Hat 11.5.0-2)

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

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

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

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

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

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

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

Ubuntu 24.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

RHEL8
	Kernel: Depends on container host
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)

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/33202/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-05-17 16:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250517151736.2565461-4-wathsala.vithanage@arm.com>
2025-05-17 14:43 ` |SUCCESS| pw153504-153506 [RFC PATCH v4 3/3] ethdev: introduce the cache stashing hints API qemudev
2025-05-17 14:47 ` qemudev
2025-05-17 15:18 ` |SUCCESS| pw153506 " checkpatch
2025-05-17 15:49 ` |FAILURE| pw153504-153506 [PATCH] [RFC,v4,3/3] ethdev: introduce the dpdklab
2025-05-17 15:53 ` |SUCCESS| " dpdklab
2025-05-17 15:53 ` dpdklab
2025-05-17 15:55 ` |PENDING| " dpdklab
2025-05-17 15:55 ` |SUCCESS| " dpdklab
2025-05-17 16:00 ` |PENDING| " dpdklab
2025-05-17 16:02 ` |FAILURE| " dpdklab
2025-05-17 16:03 ` |SUCCESS| " dpdklab
2025-05-17 16:04 ` |FAILURE| " dpdklab
2025-05-17 16:04 ` dpdklab
2025-05-17 16:05 ` dpdklab
2025-05-17 16:06 ` |SUCCESS| " dpdklab
2025-05-17 16:10 ` |WARNING| " dpdklab
2025-05-17 16:17 ` |SUCCESS| " dpdklab
2025-05-17 16:19 ` dpdklab
2025-05-17 16:24 ` |FAILURE| pw153506 [RFC PATCH v4 3/3] ethdev: introduce the cache stashing hints API 0-day Robot
2025-05-17 16:41 ` |SUCCESS| pw153504-153506 [PATCH] [RFC,v4,3/3] ethdev: introduce the dpdklab
2025-05-17 16:48 ` |WARNING| " dpdklab
2025-05-17 16:54 ` dpdklab
2025-05-17 16:56 ` dpdklab [this message]
2025-05-17 17:40 ` |FAILURE| " dpdklab
2025-05-17 20:15 ` |SUCCESS| " dpdklab
2025-05-17 21:45 ` 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=6828bfb6.c80a0220.d652b.b4e1SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=wathsala.vithanage@arm.com \
    /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).