From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw158097 [PATCH v4 3/3] dts: add virtio forwarding test suite
Date: Fri, 24 Oct 2025 16:19:07 -0400 [thread overview]
Message-ID: <20251024201907.2643627-1-robot@bytheb.org> (raw)
In-Reply-To: <20251024185056.607160-3-dmarx@iol.unh.edu>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/158097/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/18789686078
next prev parent reply other threads:[~2025-10-24 20:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251024185056.607160-3-dmarx@iol.unh.edu>
2025-10-24 18:35 ` |SUCCESS| pw158095-158097 " qemudev
2025-10-24 18:40 ` qemudev
2025-10-24 18:51 ` |SUCCESS| pw158097 " checkpatch
2025-10-24 19:29 ` |FAILURE| pw158095-158097 [PATCH] [v4,3/3] dts: add virtio forwardin dpdklab
2025-10-24 19:31 ` |PENDING| " dpdklab
2025-10-24 19:34 ` |SUCCESS| " dpdklab
2025-10-24 19:40 ` dpdklab
2025-10-24 19:45 ` |PENDING| " dpdklab
2025-10-24 19:49 ` |WARNING| " dpdklab
2025-10-24 19:58 ` |SUCCESS| " dpdklab
2025-10-24 20:08 ` |PENDING| " dpdklab
2025-10-24 20:08 ` |SUCCESS| " dpdklab
2025-10-24 20:18 ` |PENDING| " dpdklab
2025-10-24 20:19 ` 0-day Robot [this message]
2025-10-24 20:19 ` |SUCCESS| pw158097 [PATCH v4 3/3] dts: add virtio forwarding test suite 0-day Robot
2025-10-24 20:40 ` |SUCCESS| pw158095-158097 [PATCH] [v4,3/3] dts: add virtio forwardin dpdklab
2025-10-24 21:02 ` dpdklab
2025-10-24 21:03 ` dpdklab
2025-10-24 21:08 ` dpdklab
2025-10-24 21:10 ` |WARNING| " dpdklab
2025-10-24 21:48 ` |SUCCESS| " dpdklab
2025-10-24 22:10 ` dpdklab
2025-10-24 23:12 ` dpdklab
2025-10-24 23:25 ` dpdklab
2025-10-25 0:13 ` dpdklab
2025-10-25 18:43 ` |WARNING| " dpdklab
2025-10-25 18:46 ` |PENDING| " dpdklab
2025-10-25 19:28 ` |WARNING| " 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=20251024201907.2643627-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).