From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: bingz@nvidia.com, robot@bytheb.org
Subject: |FAILURE| pw154801 [PATCH v3 5/5] net/mlx5: use consecutive memory for Tx queue creation
Date: Fri, 27 Jun 2025 14:07:08 -0400 [thread overview]
Message-ID: <20250627180708.23044-1-robot@bytheb.org> (raw)
In-Reply-To: <20250627163729.50460-6-bingz@nvidia.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/154801/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/15931505691
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-stdatomic" failed at step Build and test
"fedora:39-gcc" failed at step Build
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-stdatomic" at step Build and test
####################################################################################
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-stdatomic" at step Build and test
####################################################################################
####################################################################################
#### [Begin job log] "fedora:39-gcc" at step Build
####################################################################################
####################################################################################
#### [End job log] "fedora:39-gcc" at step Build
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2025-06-27 18:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250627163729.50460-6-bingz@nvidia.com>
2025-06-27 16:05 ` |SUCCESS| pw154799-154801 " qemudev
2025-06-27 16:10 ` qemudev
2025-06-27 16:37 ` |SUCCESS| pw154801 " checkpatch
2025-06-27 18:07 ` 0-day Robot [this message]
2025-06-27 19:04 ` |SUCCESS| pw154799-154801 [PATCH] [v3,5/5] net/mlx5: use consecutive dpdklab
2025-06-27 19:08 ` dpdklab
2025-06-27 19:23 ` |FAILURE| " dpdklab
2025-06-27 19:27 ` dpdklab
2025-06-27 20:00 ` dpdklab
2025-06-27 20:04 ` |PENDING| " dpdklab
2025-06-27 20:49 ` |SUCCESS| " dpdklab
2025-06-27 20:50 ` |FAILURE| " dpdklab
2025-06-27 21:01 ` |SUCCESS| " dpdklab
2025-06-27 21:36 ` dpdklab
2025-06-27 22:00 ` |FAILURE| " dpdklab
2025-06-27 22:42 ` dpdklab
2025-06-27 23:00 ` dpdklab
2025-06-27 23:01 ` dpdklab
2025-06-27 23:04 ` dpdklab
2025-06-27 23:06 ` dpdklab
2025-06-27 23:08 ` dpdklab
2025-06-27 23:12 ` |WARNING| " dpdklab
2025-06-27 23:16 ` |PENDING| " dpdklab
2025-06-27 23:32 ` |FAILURE| " dpdklab
2025-06-27 23:53 ` |SUCCESS| " dpdklab
2025-06-27 23:54 ` dpdklab
2025-06-27 23:55 ` dpdklab
2025-06-27 23:56 ` |PENDING| " dpdklab
2025-06-28 0:03 ` |FAILURE| " dpdklab
2025-06-28 0:32 ` 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=20250627180708.23044-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=bingz@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).