From: Patrick Robb <probb@iol.unh.edu>
To: thomas@monjalon.net
Cc: web@dpdk.org, shaibran@amazon.com, zhoumin@loongson.cn,
aconole@redhat.com, rajesh.t.puttaswamy@intel.com,
Patrick Robb <probb@iol.unh.edu>
Subject: [PATCH] update testing page test recheck support lab list
Date: Fri, 25 Jul 2025 12:30:57 -0400 [thread overview]
Message-ID: <20250725163057.1059638-1-probb@iol.unh.edu> (raw)
Loongson Lab and AWS Lab have both added additional support for the
DPDK test recheck framework in recent months. This patch adds updates
the testing page to reflect that fact.
Signed-off-by: Patrick Robb <probb@iol.unh.edu>
---
content/testing/_index.md | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/content/testing/_index.md b/content/testing/_index.md
index 31b464c..bd5a6dc 100644
--- a/content/testing/_index.md
+++ b/content/testing/_index.md
@@ -133,9 +133,10 @@ when sending your recheck email. An example usage is provided below:
Recheck-request: rebase=main, iol-intel-Functional, iol-intel-Performance
```
-Rechecks are 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".
-IOL is the only lab supporting the re-apply (rebase) option.
+Rechecks are currently supported by the UNH-IOL Community Lab, the GitHub Actions Robot,
+the Loongson Lab, and the AWS Lab. From that group, UNH-IOL, Loongson, and AWS support
+the rebase argument, and the Github Robot does not. The Intel lab does not have any
+support for rechecks.
### Mainline Monitoring
--
2.49.0
reply other threads:[~2025-07-25 16:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250725163057.1059638-1-probb@iol.unh.edu \
--to=probb@iol.unh.edu \
--cc=aconole@redhat.com \
--cc=rajesh.t.puttaswamy@intel.com \
--cc=shaibran@amazon.com \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
--cc=zhoumin@loongson.cn \
/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).