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, Bing Zhao <bingz@nvidia.com>
Subject: |FAILURE| pw152060 [PATCH] [v3] net/mlx5: add eCPRI support
Date: Sat, 01 Mar 2025 11:01:37 -0800 (PST)	[thread overview]
Message-ID: <67c35991.050a0220.870a0.8e3eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250226071724.12769-1-bingz@nvidia.com>

Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/152060

_Testing issues_

Submitter: Bing Zhao <bingz@nvidia.com>
Date: Wednesday, February 26 2025 07:17:24 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5813fc4238f10b5cc2aa008b0116c977712820d7

152060 --> testing issues

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

Test environment and result as below:

+-------------------+--------------------+-------------------+------------------+
|    Environment    | dpdk_meson_compile | dpdk_compile_spdk | dpdk_compile_ovs |
+===================+====================+===================+==================+
| CentOS Stream 10  | PASS               | SKIPPED           | SKIPPED          |
+-------------------+--------------------+-------------------+------------------+
| CentOS Stream 9   | PEND               | PEND              | SKIPPED          |
+-------------------+--------------------+-------------------+------------------+
| Debian 12         | PEND               | PEND              | SKIPPED          |
+-------------------+--------------------+-------------------+------------------+
| Debian Bullseye   | FAIL               | WARN              | SKIPPED          |
+-------------------+--------------------+-------------------+------------------+
| Fedora 40         | PEND               | PEND              | SKIPPED          |
+-------------------+--------------------+-------------------+------------------+
| Fedora 41 (Clang) | PEND               | PEND              | PEND             |
+-------------------+--------------------+-------------------+------------------+
| Fedora 40 (Clang) | PEND               | PEND              | SKIPPED          |
+-------------------+--------------------+-------------------+------------------+
| openSUSE Leap 15  | PEND               | SKIPPED           | SKIPPED          |
+-------------------+--------------------+-------------------+------------------+
| Fedora 41         | PEND               | PEND              | PEND             |
+-------------------+--------------------+-------------------+------------------+
| RHEL8             | PEND               | SKIPPED           | SKIPPED          |
+-------------------+--------------------+-------------------+------------------+
| RHEL9             | PEND               | SKIPPED           | SKIPPED          |
+-------------------+--------------------+-------------------+------------------+

==== 20 line log output for Debian Bullseye (dpdk_compile_spdk): ====
 --- Failed to get log output --- 
==== 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

Debian Bullseye
	Kernel: Depends on container host
	Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110

Fedora 40
	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)

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

openSUSE Leap 15
	Kernel: Depends on container host
	Compiler: gcc (SUSE Linux) 7.5.0

Fedora 41
	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)

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-03-01 19:01 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250226071724.12769-1-bingz@nvidia.com>
2025-02-26  6:43 ` |SUCCESS| pw152060 [PATCH v3] " qemudev
2025-02-26  6:47 ` qemudev
2025-02-26  7:19 ` checkpatch
2025-02-26  8:04 ` 0-day Robot
2025-03-01 14:57 ` |SUCCESS| pw152060 [PATCH] [v3] " dpdklab
2025-03-01 14:59 ` dpdklab
2025-03-01 14:59 ` dpdklab
2025-03-01 15:12 ` dpdklab
2025-03-01 15:24 ` dpdklab
2025-03-01 15:33 ` dpdklab
2025-03-01 15:54 ` dpdklab
2025-03-01 16:17 ` dpdklab
2025-03-01 16:19 ` dpdklab
2025-03-01 16:20 ` dpdklab
2025-03-01 16:32 ` dpdklab
2025-03-01 16:35 ` dpdklab
2025-03-01 16:39 ` dpdklab
2025-03-01 16:43 ` dpdklab
2025-03-01 16:50 ` dpdklab
2025-03-01 18:02 ` |PENDING| " dpdklab
2025-03-01 18:10 ` |FAILURE| " dpdklab
2025-03-01 18:15 ` |PENDING| " dpdklab
2025-03-01 18:23 ` |WARNING| " dpdklab
2025-03-01 18:26 ` |SUCCESS| " dpdklab
2025-03-01 18:31 ` |FAILURE| " dpdklab
2025-03-01 18:35 ` dpdklab
2025-03-01 19:00 ` |WARNING| " dpdklab
2025-03-01 19:01 ` dpdklab [this message]
2025-03-01 19:02 ` |FAILURE| " dpdklab
2025-03-01 19:19 ` |SUCCESS| " dpdklab
2025-03-01 19:42 ` |FAILURE| " dpdklab
2025-03-01 19:42 ` dpdklab
2025-03-01 22:25 ` dpdklab
2025-03-02  2:12 ` |WARNING| " dpdklab
2025-03-02  2:25 ` dpdklab
2025-03-02  7:03 ` |FAILURE| " dpdklab
2025-03-02  7:08 ` dpdklab
2025-03-02 18:43 ` |WARNING| " dpdklab
2025-03-02 18:47 ` 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=67c35991.050a0220.870a0.8e3eSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bingz@nvidia.com \
    --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).