From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: shaiq.wani@intel.com, robot@bytheb.org
Subject: |FAILURE| pw157169 [PATCH v5 2/2] net/idpf: enable AVX2 for split queue Tx
Date: Wed, 1 Oct 2025 05:06:39 -0400 [thread overview]
Message-ID: <20251001090639.2714017-1-robot@bytheb.org> (raw)
In-Reply-To: <20251001075609.2608021-3-shaiq.wani@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/157169/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/18155956431
next prev parent reply other threads:[~2025-10-01 9:06 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251001075609.2608021-3-shaiq.wani@intel.com>
2025-10-01 7:21 ` |FAILURE| pw157168-157169 " qemudev
2025-10-01 7:57 ` |SUCCESS| pw157169 " checkpatch
2025-10-01 8:44 ` |SUCCESS| pw157168-157169 [PATCH] [v5,2/2] net/idpf: enable AVX2 for dpdklab
2025-10-01 8:47 ` |FAILURE| " dpdklab
2025-10-01 8:48 ` |PENDING| " dpdklab
2025-10-01 8:53 ` |FAILURE| " dpdklab
2025-10-01 8:55 ` |SUCCESS| " dpdklab
2025-10-01 9:02 ` dpdklab
2025-10-01 9:06 ` 0-day Robot [this message]
2025-10-01 9:14 ` dpdklab
2025-10-01 9:18 ` dpdklab
2025-10-01 9:36 ` dpdklab
2025-10-01 9:41 ` dpdklab
2025-10-01 9:42 ` dpdklab
2025-10-01 9:45 ` dpdklab
2025-10-01 9:51 ` dpdklab
2025-10-01 10:02 ` dpdklab
2025-10-01 10:15 ` dpdklab
2025-10-01 15:36 ` dpdklab
2025-10-02 8:08 ` |FAILURE| " dpdklab
2025-10-02 8:10 ` dpdklab
2025-10-02 8:11 ` dpdklab
2025-10-02 8:14 ` dpdklab
2025-10-02 8:17 ` dpdklab
2025-10-02 8:21 ` dpdklab
2025-10-02 8:21 ` dpdklab
2025-10-02 8:23 ` dpdklab
2025-10-02 8:24 ` dpdklab
2025-10-02 8:28 ` dpdklab
2025-10-02 8:30 ` dpdklab
2025-10-02 8:31 ` dpdklab
2025-10-02 8:35 ` dpdklab
2025-10-02 10:21 ` dpdklab
2025-10-02 13:59 ` 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=20251001090639.2714017-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=shaiq.wani@intel.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).