From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw157813 [PATCH v2 2/2] usertools/dpdk-telemetry-client: correct script formatting
Date: Fri, 17 Oct 2025 11:40:29 -0400 [thread overview]
Message-ID: <20251017154029.2067789-1-robot@bytheb.org> (raw)
In-Reply-To: <20251017141927.1156370-3-bruce.richardson@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/157813/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/18595912709
next prev parent reply other threads:[~2025-10-17 15:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251017141927.1156370-3-bruce.richardson@intel.com>
2025-10-17 14:01 ` |SUCCESS| pw157812-157813 " qemudev
2025-10-17 14:06 ` qemudev
2025-10-17 14:19 ` |SUCCESS| pw157813 " checkpatch
2025-10-17 14:44 ` |PENDING| pw157812-157813 [PATCH] [v2,2/2] usertools/dpdk-telemetry- dpdklab
2025-10-17 14:45 ` dpdklab
2025-10-17 14:46 ` |SUCCESS| " dpdklab
2025-10-17 14:48 ` dpdklab
2025-10-17 14:54 ` |PENDING| " dpdklab
2025-10-17 14:58 ` dpdklab
2025-10-17 15:00 ` |SUCCESS| " dpdklab
2025-10-17 15:03 ` dpdklab
2025-10-17 15:05 ` dpdklab
2025-10-17 15:05 ` dpdklab
2025-10-17 15:07 ` dpdklab
2025-10-17 15:11 ` dpdklab
2025-10-17 15:40 ` 0-day Robot [this message]
2025-10-17 15:40 ` |SUCCESS| pw157813 [PATCH v2 2/2] usertools/dpdk-telemetry-client: correct script formatting 0-day Robot
2025-10-17 16:00 ` |SUCCESS| pw157812-157813 [PATCH] [v2,2/2] usertools/dpdk-telemetry- dpdklab
2025-10-17 16:09 ` dpdklab
2025-10-17 16:54 ` dpdklab
2025-10-17 17:48 ` dpdklab
2025-10-17 18:07 ` dpdklab
2025-10-17 21:09 ` |PENDING| " dpdklab
2025-10-17 22:31 ` |WARNING| " dpdklab
2025-10-17 23:16 ` dpdklab
2025-10-17 23:43 ` |SUCCESS| " dpdklab
2025-10-18 7:00 ` 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=20251017154029.2067789-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).