DPDK CI discussions
 help / color / mirror / Atom feed
From: zhoumin <zhoumin@loongson.cn>
To: Patrick Robb <probb@iol.unh.edu>
Cc: ci@dpdk.org, Aaron Conole <aconole@redhat.com>,
	David Marchand <david.marchand@redhat.com>,
	"Brandes, Shai" <shaibran@amazon.com>
Subject: Re: Email based retests for the Loongarch lab
Date: Thu, 17 Jul 2025 20:48:57 +0800	[thread overview]
Message-ID: <404eaac9-72da-ffba-3d59-eb2617df03b8@loongson.cn> (raw)
In-Reply-To: <CAJvnSUBsAA4R54xJwUoeQzoDjLpUV_6d0Np4cEgZftXK4Yr7ig@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]

Hi Patrick Robb,

On 2025/7/9 8:49AM, Patrick Robb wrote:
> Hi Zhoumin,
>
> Aaron did approve the get_reruns.py patch for the rebase arg and merge 
> it to dpdk-ci. So, you are good to pull that into your dpdk-ci fork.
>
Thanks for your contributions. I have used this script to support the 
retest with rebase arg in Loongson lab.
> On Tue, Jun 17, 2025 at 12:16 AM zhoumin <zhoumin@loongson.cn 
> <mailto:zhoumin@loongson.cn>> wrote:
>
>>     Maybe you can apply it, give it a run and add a tested by tag to
>>     the patch if it is working for you?
>     Yes, I have tested it and it is working for me. This patch has a
>     little changes in the inputs and outputs to get_reruns.py, and I
>     need to make corresponding changes to our current implementation
>     of retest.
>>
> Okay, thanks. When you get the free time to implement these change 
> please ping me so I know we are ready for any next steps (like 
> updating the labs recheck support status on the DPDK website).
We support the rebase arg now when request to retest. But there maybe a 
little difference between Loongson lab and other labs. We recheck the 
patches on the latest HEAD of the branch specified by rebase arg if has 
or selected by pw_maintainers_cli.py script. I want to know if there 
will be any problems with this behaviour? Is it acceptable?


[-- Attachment #2: Type: text/html, Size: 3381 bytes --]

      reply	other threads:[~2025-07-17 12:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22  5:55 Patrick Robb
2024-02-22 13:54 ` Patrick Robb
2024-02-28  5:34   ` zhoumin
2024-02-29  6:09     ` Patrick Robb
2024-03-01 10:19       ` zhoumin
2025-05-28 19:36         ` Patrick Robb
2025-06-08  0:49           ` zhoumin
2025-06-11 21:05             ` Patrick Robb
2025-06-17  4:15               ` zhoumin
2025-07-09 12:49                 ` Patrick Robb
2025-07-17 12:48                   ` zhoumin [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=404eaac9-72da-ffba-3d59-eb2617df03b8@loongson.cn \
    --to=zhoumin@loongson.cn \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=probb@iol.unh.edu \
    --cc=shaibran@amazon.com \
    /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).