automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw157155 [PATCH v3 5/5] usertools/mbuf: parse mbuf history dump
Date: Tue, 30 Sep 2025 21:28:21 -0400	[thread overview]
Message-ID: <20251001012821.3602301-1-robot@bytheb.org> (raw)
In-Reply-To: <20250930233828.3999565-6-thomas@monjalon.net>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/157155/

_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/18147073426

  parent reply	other threads:[~2025-10-01  1:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250930233828.3999565-6-thomas@monjalon.net>
2025-09-30 23:05 ` |SUCCESS| pw157151-157155 " qemudev
2025-09-30 23:10 ` qemudev
2025-09-30 23:39 ` |SUCCESS| pw157155 " checkpatch
2025-10-01  0:13 ` |SUCCESS| pw157151-157155 [PATCH] [v3,5/5] usertools/mbuf: parse mbu dpdklab
2025-10-01  0:17 ` |PENDING| " dpdklab
2025-10-01  0:18 ` dpdklab
2025-10-01  0:20 ` |SUCCESS| " dpdklab
2025-10-01  0:30 ` dpdklab
2025-10-01  0:31 ` dpdklab
2025-10-01  0:38 ` dpdklab
2025-10-01  0:53 ` dpdklab
2025-10-01  0:54 ` dpdklab
2025-10-01  1:04 ` dpdklab
2025-10-01  1:09 ` dpdklab
2025-10-01  1:13 ` dpdklab
2025-10-01  1:28 ` dpdklab
2025-10-01  1:28 ` 0-day Robot [this message]
2025-10-01  1:28 ` |SUCCESS| pw157155 [PATCH v3 5/5] usertools/mbuf: parse mbuf history dump 0-day Robot
2025-10-01 12:20 ` |SUCCESS| pw157151-157155 [PATCH] [v3,5/5] usertools/mbuf: parse mbu dpdklab
2025-10-01 12:49 ` dpdklab
2025-10-01 13:07 ` dpdklab
2025-10-01 14:39 ` dpdklab
2025-10-01 16:39 ` dpdklab
2025-10-01 18:22 ` dpdklab
2025-10-01 19:39 ` dpdklab
2025-10-01 22:06 ` dpdklab
2025-10-03  2:06 ` dpdklab
2025-10-03  8:35 ` 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=20251001012821.3602301-1-robot@bytheb.org \
    --to=robot@bytheb.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).