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,
	Tirthendu Sarkar <tirthendu.sarkar@intel.com>
Subject: |FAILURE| pw152790 [PATCH] [v3] event/dlb2: consolidate AVX512 and S
Date: Mon, 07 Apr 2025 09:29:35 -0700 (PDT)	[thread overview]
Message-ID: <67f3fd6f.050a0220.368b93.cf51SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250407091925.3057365-1-tirthendu.sarkar@intel.com>

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

_Testing issues_

Submitter: Tirthendu Sarkar <tirthendu.sarkar@intel.com>
Date: Monday, April 07 2025 09:19:25 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e30e194c4d06cf9b0e93f9f0f2a289bef96abc1a

152790 --> testing issues

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

Test environment and result as below:

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

==== Unit test summary for Ubuntu 20.04 (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)

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

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

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

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

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

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

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

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

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

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

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

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-07 16:29 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250407091925.3057365-1-tirthendu.sarkar@intel.com>
2025-04-07  8:53 ` |SUCCESS| pw152790 [PATCH v3] event/dlb2: consolidate AVX512 and SSE changes qemudev
2025-04-07  8:57 ` qemudev
2025-04-07  9:19 ` |WARNING| " checkpatch
2025-04-07 10:22 ` |SUCCESS| " 0-day Robot
2025-04-07 14:09 ` |SUCCESS| pw152790 [PATCH] [v3] event/dlb2: consolidate AVX512 and S dpdklab
2025-04-07 14:10 ` dpdklab
2025-04-07 14:15 ` dpdklab
2025-04-07 14:19 ` |PENDING| " dpdklab
2025-04-07 14:20 ` |SUCCESS| " dpdklab
2025-04-07 14:32 ` dpdklab
2025-04-07 14:35 ` |WARNING| " dpdklab
2025-04-07 14:41 ` |FAILURE| " dpdklab
2025-04-07 14:42 ` |PENDING| " dpdklab
2025-04-07 14:45 ` |SUCCESS| " dpdklab
2025-04-07 14:46 ` |FAILURE| " dpdklab
2025-04-07 14:57 ` |WARNING| " dpdklab
2025-04-07 15:04 ` |SUCCESS| " dpdklab
2025-04-07 15:06 ` dpdklab
2025-04-07 15:06 ` |WARNING| " dpdklab
2025-04-07 15:07 ` |SUCCESS| " dpdklab
2025-04-07 15:09 ` |FAILURE| " dpdklab
2025-04-07 15:18 ` |WARNING| " dpdklab
2025-04-07 15:22 ` dpdklab
2025-04-07 16:29 ` dpdklab [this message]
2025-04-07 16:32 ` |FAILURE| " dpdklab
2025-04-07 16:34 ` dpdklab
2025-04-07 16:45 ` dpdklab
2025-04-07 17:32 ` |SUCCESS| " dpdklab
2025-04-07 17:36 ` 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=67f3fd6f.050a0220.368b93.cf51SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=tirthendu.sarkar@intel.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).