From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw156794 [PATCH 3/3] app/compress-perf: support for dictionaries and PDCP checksum
Date: Fri, 19 Sep 2025 18:03:12 -0400 [thread overview]
Message-ID: <20250919220312.1061455-1-robot@bytheb.org> (raw)
In-Reply-To: <20250919210253.2664545-3-svaze@qti.qualcomm.com>
From: robot@bytheb.org
Test-Label: github-robot-post
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/156794/
_github post: success_
HTML Link: https://github.com/ovsrobot/dpdk/pull/73
next prev parent reply other threads:[~2025-09-19 22:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250919210253.2664545-3-svaze@qti.qualcomm.com>
2025-09-19 20:29 ` |SUCCESS| pw156792-156794 " qemudev
2025-09-19 20:34 ` qemudev
2025-09-19 21:01 ` |WARNING| pw156794 " checkpatch
2025-09-19 21:50 ` |SUCCESS| pw156792-156794 [PATCH] [3/3] app/compress-perf: support f dpdklab
2025-09-19 21:51 ` |PENDING| " dpdklab
2025-09-19 21:53 ` |SUCCESS| " dpdklab
2025-09-19 22:03 ` |SUCCESS| pw156794 [PATCH 3/3] app/compress-perf: support for dictionaries and PDCP checksum 0-day Robot
2025-09-19 22:03 ` 0-day Robot [this message]
2025-09-19 22:06 ` |FAILURE| pw156792-156794 [PATCH] [3/3] app/compress-perf: support f dpdklab
2025-09-19 22:08 ` |PENDING| " dpdklab
2025-09-19 22:15 ` dpdklab
2025-09-19 22:16 ` |SUCCESS| " dpdklab
2025-09-19 22:20 ` dpdklab
2025-09-19 22:24 ` dpdklab
2025-09-19 22:24 ` dpdklab
2025-09-19 22:32 ` dpdklab
2025-09-19 22:46 ` |FAILURE| " dpdklab
2025-09-19 22:48 ` dpdklab
2025-09-19 23:03 ` |SUCCESS| " dpdklab
2025-09-19 23:14 ` dpdklab
2025-09-19 23:16 ` |FAILURE| " dpdklab
2025-09-19 23:19 ` |SUCCESS| " dpdklab
2025-09-19 23:25 ` dpdklab
2025-09-19 23:26 ` dpdklab
2025-09-19 23:37 ` |FAILURE| " dpdklab
2025-09-19 23:48 ` |SUCCESS| " dpdklab
2025-09-20 0:05 ` 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=20250919220312.1061455-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).