automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: stephen@networkplumber.org, robot@bytheb.org
Subject: |FAILURE| pw159154 [PATCH] test: skip hash tests from other CPU
Date: Thu,  4 Dec 2025 21:03:44 -0500	[thread overview]
Message-ID: <20251205020344.2909367-1-robot@bytheb.org> (raw)
In-Reply-To: <20251205002536.192437-1-stephen@networkplumber.org>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/159154/

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/19949284538

  parent reply	other threads:[~2025-12-05  2:03 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251205002536.192437-1-stephen@networkplumber.org>
2025-12-04 23:52 ` |SUCCESS| " qemudev
2025-12-04 23:57 ` qemudev
2025-12-05  0:26 ` checkpatch
2025-12-05  2:03 ` 0-day Robot [this message]
2025-12-05  3:10 ` |PENDING| " dpdklab
2025-12-05  3:14 ` |SUCCESS| " dpdklab
2025-12-05  3:17 ` dpdklab
2025-12-05  3:22 ` dpdklab
2025-12-05  4:28 ` |PENDING| " dpdklab
2025-12-05  4:43 ` |SUCCESS| " dpdklab
2025-12-05  4:59 ` dpdklab
2025-12-05  5:47 ` dpdklab
2025-12-05  6:41 ` |PENDING| " dpdklab
2025-12-05  7:04 ` |SUCCESS| " dpdklab
2025-12-05  7:05 ` dpdklab
2025-12-05  8:37 ` dpdklab
2025-12-05  9:34 ` dpdklab
2025-12-05 10:58 ` dpdklab
2025-12-05 11:05 ` dpdklab
2025-12-05 11:11 ` dpdklab
2025-12-05 13:11 ` dpdklab
2025-12-05 14:05 ` dpdklab
2025-12-05 14:06 ` dpdklab
2025-12-05 14:13 ` dpdklab
2025-12-05 14:14 ` |PENDING| " dpdklab
2025-12-05 14:32 ` |SUCCESS| " dpdklab
2025-12-05 14:34 ` dpdklab
2025-12-05 14:49 ` |FAILURE| " dpdklab
2025-12-05 15:05 ` |SUCCESS| " dpdklab
2025-12-05 22:54 ` dpdklab
2025-12-06  0:02 ` 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=20251205020344.2909367-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=stephen@networkplumber.org \
    --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).