DPDK website maintenance
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: web@dpdk.org
Cc: Patrick Robb <probb@iol.unh.edu>
Subject: [PATCH 1/1] adding retest request instructions to the dpdk website
Date: Wed, 30 Aug 2023 23:18:34 -0400	[thread overview]
Message-ID: <20230831031834.9271-2-probb@iol.unh.edu> (raw)
In-Reply-To: <20230831031834.9271-1-probb@iol.unh.edu>

Signed-off-by: Patrick Robb <probb@iol.unh.edu>
 content/testing/_index.md | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/content/testing/_index.md b/content/testing/_index.md
index 1a31e5f..86fcbab 100644
--- a/content/testing/_index.md
+++ b/content/testing/_index.md
@@ -103,6 +103,15 @@ referencing the report archive and incrementing one of the counters
 A maintainer should wait the end of the tests (should be less than a day),
 and check the results before accepting a patch.
+### Requesting a Patch Retest
+If CI testing reports a FAIL for a test label on Patchwork, it is possible to request a retest of your patchseries on those label(s).
+For a list of Patchwork testing labels, send an email reply on your patch series cover letter or patch email like so:
+Recheck-request: iol-compile-amd64-testing, iol-broadcom-Performance, iol-compile-arm64-testing
+This is currently only supported by the UNH-IOL Community Lab. So, just those Patchwork testing labels beginning wih "iol."
 ### Mainline Monitoring
 The repository mirror on [GitHub](//github.com/DPDK/dpdk)

  reply	other threads:[~2023-08-31  3:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31  3:18 [PATCH 0/1] add retesting framework instructions Patrick Robb
2023-08-31  3:18 ` Patrick Robb [this message]
2023-11-01 15:43   ` [PATCH 1/1] adding retest request instructions to the dpdk website 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230831031834.9271-2-probb@iol.unh.edu \
    --to=probb@iol.unh.edu \
    --cc=web@dpdk.org \


* 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).