From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw153874 [PATCH v2 3/3] app/eventdev: add vector adapter performance test
Date: Thu, 29 May 2025 19:44:01 -0400 [thread overview]
Message-ID: <20250529234401.3095013-1-robot@bytheb.org> (raw)
In-Reply-To: <20250529222437.91818-4-pbhagavatula@marvell.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/153874/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/15335102525
next prev parent reply other threads:[~2025-05-29 23:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250529222437.91818-4-pbhagavatula@marvell.com>
2025-05-29 21:51 ` |SUCCESS| pw153872-153874 " qemudev
2025-05-29 21:56 ` qemudev
2025-05-29 22:25 ` |SUCCESS| pw153874 " checkpatch
2025-05-29 23:44 ` 0-day Robot [this message]
2025-05-30 5:12 ` |SUCCESS| pw153872-153874 [PATCH] [v2,3/3] app/eventdev: add vector dpdklab
2025-05-30 6:39 ` |PENDING| " dpdklab
2025-05-30 6:42 ` dpdklab
2025-05-30 7:12 ` dpdklab
2025-05-30 7:14 ` |SUCCESS| " dpdklab
2025-05-30 7:24 ` |PENDING| " dpdklab
2025-05-30 8:12 ` |SUCCESS| " dpdklab
2025-05-30 8:13 ` dpdklab
2025-05-30 8:14 ` dpdklab
2025-05-30 8:15 ` dpdklab
2025-05-30 8:15 ` dpdklab
2025-05-30 8:16 ` dpdklab
2025-05-30 8:17 ` dpdklab
2025-05-30 9:20 ` |PENDING| " dpdklab
2025-05-30 9:46 ` |WARNING| " dpdklab
2025-05-30 9:47 ` dpdklab
2025-05-30 9:49 ` dpdklab
2025-05-30 9:49 ` dpdklab
2025-05-30 9:50 ` dpdklab
2025-05-30 9:51 ` dpdklab
2025-05-30 13:53 ` dpdklab
2025-05-30 17:44 ` |SUCCESS| " dpdklab
2025-05-30 17:53 ` dpdklab
2025-05-30 22:54 ` |WARNING| " dpdklab
2025-05-30 23:01 ` dpdklab
2025-05-31 4:16 ` |SUCCESS| " dpdklab
2025-05-31 6:05 ` dpdklab
2025-05-31 6:38 ` dpdklab
2025-06-04 15:11 ` 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=20250529234401.3095013-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).