DPDK website maintenance
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: web@dpdk.org
Cc: probb@iol.unh.edu
Subject: [PATCH] testing: add the GitHub Actions robot to retest instructions
Date: Thu,  4 Jan 2024 10:10:47 -0500	[thread overview]
Message-ID: <20240104151047.437236-1-aconole@redhat.com> (raw)

Signed-off-by: Aaron Conole <aconole@redhat.com>
---
 content/testing/_index.md | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/content/testing/_index.md b/content/testing/_index.md
index 1db5927..a054292 100644
--- a/content/testing/_index.md
+++ b/content/testing/_index.md
@@ -106,14 +106,17 @@ and check the results before accepting a patch.
 #### Requesting a Patch Retest
 
 If CI reports a failure for a test label on Patchwork,
-it is possible to request a retest of a patch series on those label(s).
+it is possible to request a retest of a patch or series on those label(s).
 For a list of Patchwork testing labels, send an email reply on the patch or cover letter like so:
 ```
-Recheck-request: iol-compile-amd64-testing, iol-broadcom-Performance, iol-unit-arm64-testing
+Recheck-request: iol-compile-amd64-testing, iol-broadcom-Performance, iol-unit-arm64-testing, github-robot
 ```
 
-This is currently only supported by the UNH-IOL Community Lab,
-so just those Patchwork testing labels beginning wih "iol-".
+Note that you may omit any labels which are not failing.
+
+This is currently supported by the UNH-IOL Community Lab, and the GitHub
+Actions robot so just those Patchwork testing labels beginning wih "iol-"
+or "github-robot".
 
 ### Mainline Monitoring
 
-- 
2.41.0


             reply	other threads:[~2024-01-04 15:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04 15:10 Aaron Conole [this message]
2024-01-04 16:17 ` Jeremy Spewock
2024-01-05 13:22 ` Thomas Monjalon

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=20240104151047.437236-1-aconole@redhat.com \
    --to=aconole@redhat.com \
    --cc=probb@iol.unh.edu \
    --cc=web@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).