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| pw143302 [PATCH v1 3/3] test/crypto: add support for error recovery
Date: Thu, 22 Aug 2024 07:23:05 -0400	[thread overview]
Message-ID: <20240822112305.919388-1-robot@bytheb.org> (raw)
In-Reply-To: <20240822102856.3965710-3-vvelumuri@marvell.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2024-08-22 11:23 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240822102856.3965710-3-vvelumuri@marvell.com>
2024-08-22 10:03 ` |SUCCESS| pw143300-143302 " qemudev
2024-08-22 10:07 ` qemudev
2024-08-22 10:30 ` |SUCCESS| pw143302 " checkpatch
2024-08-22 11:23 ` 0-day Robot [this message]
2024-08-22 11:36 ` |SUCCESS| pw143300-143302 [PATCH] [v1,3/3] test/crypto: add support dpdklab
2024-08-22 11:48 ` dpdklab
2024-08-22 11:52 ` dpdklab
2024-08-22 11:53 ` dpdklab
2024-08-22 11:53 ` dpdklab
2024-08-22 12:00 ` dpdklab
2024-08-22 12:00 ` dpdklab
2024-08-22 12:01 ` dpdklab
2024-08-22 12:01 ` dpdklab
2024-08-22 12:02 ` dpdklab
2024-08-22 12:02 ` dpdklab
2024-08-22 12:03 ` dpdklab
2024-08-22 12:04 ` dpdklab
2024-08-22 12:06 ` dpdklab
2024-08-22 12:06 ` dpdklab
2024-08-22 12:06 ` dpdklab
2024-08-22 12:07 ` dpdklab
2024-08-22 12:08 ` dpdklab
2024-08-22 12:08 ` dpdklab
2024-08-22 12:09 ` dpdklab
2024-08-22 12:09 ` dpdklab
2024-08-22 12:14 ` |PENDING| " dpdklab
2024-08-22 12:16 ` |SUCCESS| " dpdklab
2024-08-22 12:17 ` dpdklab
2024-08-22 12:20 ` dpdklab
2024-08-22 12:21 ` dpdklab
2024-08-22 12:21 ` dpdklab
2024-08-22 12:23 ` dpdklab
2024-08-22 12:43 ` |PENDING| " dpdklab
2024-08-22 12:58 ` |SUCCESS| " dpdklab
2024-08-22 13:00 ` dpdklab
2024-08-22 13:01 ` dpdklab
2024-08-22 13:03 ` dpdklab
2024-08-22 13:04 ` dpdklab
2024-08-22 13:05 ` dpdklab
2024-08-22 13:05 ` dpdklab
2024-08-22 13:06 ` dpdklab
2024-08-22 13:06 ` dpdklab
2024-08-22 13:17 ` |PENDING| " dpdklab
2024-08-22 13:22 ` |FAILURE| " dpdklab
2024-08-22 13:24 ` |SUCCESS| " dpdklab
2024-08-22 13:25 ` dpdklab
2024-08-22 13:46 ` dpdklab
2024-08-22 13:56 ` |WARNING| " dpdklab
2024-08-22 13:57 ` |PENDING| " dpdklab
2024-08-22 14:34 ` |SUCCESS| " dpdklab
2024-08-22 14:36 ` dpdklab
2024-08-22 15:10 ` dpdklab
2024-08-22 15:37 ` dpdklab
2024-08-22 16:08 ` dpdklab
2024-08-22 18:33 ` dpdklab
2024-08-22 18:42 ` dpdklab
2024-08-22 18:42 ` dpdklab
2024-09-21  4:08 ` dpdklab
2024-09-21  4:20 ` dpdklab
2024-09-21  4:43 ` dpdklab
2024-09-21  5: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=20240822112305.919388-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).