From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Maayan Kashani <mkashani@nvidia.com>
Subject: |FAILURE| pw140880-140889 [PATCH] [v6,11/11] net/mlx5: initial desig
Date: Sun, 09 Jun 2024 03:05:01 -0700 (PDT) [thread overview]
Message-ID: <66657e4d.170a0220.7809a.78bdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240609085600.87274-11-mkashani@nvidia.com>
Test-Label: iol-compile-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/140889
_Testing issues_
Submitter: Maayan Kashani <mkashani@nvidia.com>
Date: Sunday, June 09 2024 08:56:00
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2bf363ff7e924a1fb6054eee693fde66097273f7
140880-140889 --> testing issues
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Debian 12 with MUSDK | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | FAIL |
+----------------------------------------+--------------------+
| Ubuntu 22.04 (ARM) | FAIL |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | FAIL |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | FAIL |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | FAIL |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | FAIL |
+----------------------------------------+--------------------+
| Ubuntu 24.04 (ARM) | FAIL |
+----------------------------------------+--------------------+
| Fedora 39 (ARM) | FAIL |
+----------------------------------------+--------------------+
| Debian 12 (arm) | FAIL |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
==== 20 line log output for Debian 12 (arm) (dpdk_meson_compile): ====
--- Failed to get log output ---
==== End log output ====
Debian 12 with MUSDK
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Ubuntu 22.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.4.0
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.4.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 24.04 (ARM)
Kernel: 5.4.0-167-generic
Compiler: gcc 13.2.0
Fedora 39 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang 10.0.0-4ubuntu1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30150/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-06-09 10:05 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240609085600.87274-11-mkashani@nvidia.com>
2024-06-09 8:32 ` |SUCCESS| pw140880-140889 [PATCH v6 11/11] net/mlx5: initial design changes qemudev
2024-06-09 8:36 ` qemudev
2024-06-09 8:58 ` |SUCCESS| pw140889 " checkpatch
2024-06-09 10:01 ` |FAILURE| pw140880-140889 [PATCH] [v6,11/11] net/mlx5: initial desig dpdklab
2024-06-09 10:02 ` dpdklab
2024-06-09 10:02 ` |WARNING| " dpdklab
2024-06-09 10:02 ` dpdklab
2024-06-09 10:03 ` dpdklab
2024-06-09 10:03 ` dpdklab
2024-06-09 10:03 ` dpdklab
2024-06-09 10:03 ` |FAILURE| " dpdklab
2024-06-09 10:03 ` dpdklab
2024-06-09 10:03 ` dpdklab
2024-06-09 10:04 ` dpdklab
2024-06-09 10:04 ` dpdklab
2024-06-09 10:04 ` |WARNING| " dpdklab
2024-06-09 10:04 ` |FAILURE| " dpdklab
2024-06-09 10:04 ` |WARNING| " dpdklab
2024-06-09 10:04 ` |FAILURE| " dpdklab
2024-06-09 10:05 ` dpdklab [this message]
2024-06-09 10:05 ` dpdklab
2024-06-09 10:05 ` dpdklab
2024-06-09 10:05 ` |WARNING| " dpdklab
2024-06-09 10:05 ` |FAILURE| " dpdklab
2024-06-09 10:05 ` dpdklab
2024-06-09 10:05 ` dpdklab
2024-06-09 10:05 ` dpdklab
2024-06-09 10:05 ` dpdklab
2024-06-09 10:06 ` dpdklab
2024-06-09 10:06 ` dpdklab
2024-06-09 10:06 ` |WARNING| " dpdklab
2024-06-09 10:06 ` |FAILURE| " dpdklab
2024-06-09 10:06 ` dpdklab
2024-06-09 10:06 ` dpdklab
2024-06-09 10:06 ` dpdklab
2024-06-09 10:07 ` dpdklab
2024-06-09 10:07 ` dpdklab
2024-06-09 10:07 ` dpdklab
2024-06-09 10:07 ` dpdklab
2024-06-09 10:07 ` dpdklab
2024-06-09 10:07 ` dpdklab
2024-06-09 10:08 ` dpdklab
2024-06-09 10:08 ` dpdklab
2024-06-09 10:08 ` dpdklab
2024-06-09 10:08 ` dpdklab
2024-06-09 10:08 ` dpdklab
2024-06-09 10:09 ` dpdklab
2024-06-09 10:09 ` dpdklab
2024-06-09 10:09 ` dpdklab
2024-06-09 10:09 ` dpdklab
2024-06-09 10:09 ` dpdklab
2024-06-09 10:09 ` dpdklab
2024-06-09 10:11 ` dpdklab
2024-06-09 10:11 ` dpdklab
2024-06-09 10:11 ` dpdklab
2024-06-09 10:11 ` dpdklab
2024-06-09 10:12 ` dpdklab
2024-06-09 10:12 ` dpdklab
2024-06-09 10:12 ` dpdklab
2024-06-09 10:12 ` dpdklab
2024-06-09 10:12 ` dpdklab
2024-06-09 10:12 ` dpdklab
2024-06-09 10:12 ` dpdklab
2024-06-09 10:13 ` dpdklab
2024-06-09 10:13 ` dpdklab
2024-06-09 10:13 ` dpdklab
2024-06-09 10:14 ` dpdklab
2024-06-09 10:14 ` dpdklab
2024-06-09 10:14 ` dpdklab
2024-06-09 10:14 ` dpdklab
2024-06-09 10:14 ` |WARNING| " dpdklab
2024-06-09 10:15 ` |FAILURE| " dpdklab
2024-06-09 10:15 ` dpdklab
2024-06-09 10:16 ` dpdklab
2024-06-09 10:33 ` dpdklab
2024-06-09 10:34 ` dpdklab
2024-06-09 10:37 ` 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=66657e4d.170a0220.7809a.78bdSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=mkashani@nvidia.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).