From: Kevin Traynor <ktraynor@redhat.com>
To: zhoumin <zhoumin@loongson.cn>, Patrick Robb <probb@iol.unh.edu>,
thomas@monjalon.net
Cc: web@dpdk.org, shaibran@amazon.com, aconole@redhat.com,
rajesh.t.puttaswamy@intel.com
Subject: Re: [PATCH] update testing page test recheck support lab list
Date: Tue, 19 Aug 2025 11:02:21 +0100 [thread overview]
Message-ID: <0daf3aa4-5405-46aa-917c-519721604f4e@redhat.com> (raw)
In-Reply-To: <de88a7f4-537e-4d63-15ea-56741e26cd6a@loongson.cn>
On 01/08/2025 07:34, zhoumin wrote:
> On 2025/7/26 12:30AM, Patrick Robb wrote:
>
>> 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
>>
> Reviewed-by: Min Zhou <zhoumin@loongson.cn>
>
> Thanks Patrick Robb.
>
>
Looks like this is ok to apply, or there are some further Acks required?
prev parent reply other threads:[~2025-08-19 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 16:30 Patrick Robb
2025-08-01 6:34 ` zhoumin
2025-08-19 10:02 ` Kevin Traynor [this message]
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=0daf3aa4-5405-46aa-917c-519721604f4e@redhat.com \
--to=ktraynor@redhat.com \
--cc=aconole@redhat.com \
--cc=probb@iol.unh.edu \
--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).