From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: getelson@nvidia.com, robot@bytheb.org
Subject: |FAILURE| pw158181 [PATCH 2/2] net/mlx5: support PF representor suppresion in multi-port E-Switch
Date: Tue, 28 Oct 2025 07:22:35 -0400 [thread overview]
Message-ID: <20251028112235.2810523-1-robot@bytheb.org> (raw)
In-Reply-To: <20251028095831.53669-2-getelson@nvidia.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/158181/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/18871621376
next prev parent reply other threads:[~2025-10-28 11:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251028095831.53669-2-getelson@nvidia.com>
2025-10-28 9:34 ` |SUCCESS| pw158180-158181 " qemudev
2025-10-28 9:39 ` |FAILURE| " qemudev
2025-10-28 10:00 ` |WARNING| pw158181 " checkpatch
2025-10-28 11:13 ` |SUCCESS| pw158180-158181 [PATCH] [2/2] net/mlx5: support PF represe dpdklab
2025-10-28 11:19 ` dpdklab
2025-10-28 11:20 ` |PENDING| " dpdklab
2025-10-28 11:22 ` |SUCCESS| " dpdklab
2025-10-28 11:22 ` 0-day Robot [this message]
2025-10-28 11:29 ` dpdklab
2025-10-28 12:10 ` dpdklab
2025-10-28 12:32 ` dpdklab
2025-10-28 12:49 ` |PENDING| " dpdklab
2025-10-28 13:11 ` dpdklab
2025-10-28 13:16 ` |SUCCESS| " dpdklab
2025-10-28 13:16 ` dpdklab
2025-10-28 13:56 ` |WARNING| " dpdklab
2025-10-28 14:52 ` |FAILURE| " dpdklab
2025-10-28 15:53 ` |WARNING| " dpdklab
2025-10-28 16:06 ` dpdklab
2025-10-28 16:10 ` |FAILURE| " dpdklab
2025-10-28 16:57 ` |SUCCESS| " dpdklab
2025-10-28 17:18 ` |WARNING| " dpdklab
2025-10-28 17:31 ` |FAILURE| " dpdklab
2025-10-28 17:44 ` |SUCCESS| " dpdklab
2025-10-28 18:05 ` |FAILURE| " dpdklab
2025-10-28 18:25 ` |SUCCESS| " dpdklab
2025-10-28 18:49 ` |FAILURE| " dpdklab
2025-10-28 20:58 ` dpdklab
2025-10-28 21:02 ` |WARNING| " dpdklab
2025-10-28 21:30 ` 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=20251028112235.2810523-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=getelson@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).