From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 87FE843B77; Thu, 22 Feb 2024 14:54:14 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 80E7540281; Thu, 22 Feb 2024 14:54:14 +0100 (CET) Received: from mail-ot1-f54.google.com (mail-ot1-f54.google.com [209.85.210.54]) by mails.dpdk.org (Postfix) with ESMTP id 6D3654027F for ; Thu, 22 Feb 2024 14:54:13 +0100 (CET) Received: by mail-ot1-f54.google.com with SMTP id 46e09a7af769-6e458a77be3so2163467a34.1 for ; Thu, 22 Feb 2024 05:54:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1708610052; x=1709214852; darn=dpdk.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=0f9D2G41AG/6KQpdTQcsIwp76efeMvvoVoF0dEUQCyw=; b=QpE5V16Ph2Vwy/2FA9X09DQkFjd44cNYKk163W2ZPnuokbWayj5f/S3A4vr7qiMKcw OaT5JKsnlGsNPqhLuouEmjmqQ5NRo6nUQ0uI4HA7AWY0F84IvgbsSZkr/2FMtEjE2v+L uxuBnfkvoL5lyr+8KgUCtwtO4twfQ+QxgScb8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708610052; x=1709214852; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=0f9D2G41AG/6KQpdTQcsIwp76efeMvvoVoF0dEUQCyw=; b=Zd4AQb0HWeF2dgvL+B/n+Wju64mrM5VfqABLGXyezHRi5dRUiK1ic6fVPLUi0e1fu7 MRQAPm8u1u6vYYucs+4HGV7dpDKT0YWWyCXJRef6apTyci4srUNPq4WyEwSw6chp5rdz JWmAjM0YEHrtMJb41N+a/rGZuPCU1o9JYTpc7/PqpfTqZGfJcK9vtlesu9Pkt/aUCzl6 /zfXW+8cGiWBXQ5cocF8WAIcT/YCs/K2h1aiyY5gG2lijaPWmkZoIW5ytXnpoPqqE+Pk 9zhK2kuU8xqD+JumbeGTuJs7CNtLD9dLc+v3WEK7AkW+Yyj95KHmDk0OIA86hreALQ05 4DJQ== X-Gm-Message-State: AOJu0YyW72DcGtYP8btB0wpnn/HvOIuHMmBYQt1CcaBPfUDHHb3Ul7kj 7lfNElvqTXpu/FnzPNyk5No8bXh4NhxpCqkushK6bp6Rn7G/msHSZg6b4/PHZCld5x3hfA9cKcm c+FTF84o0u7p0LBpiDQf4CQ1+vtn3S4zL1tWm9w== X-Google-Smtp-Source: AGHT+IEHibcwnfiMibL/UNaeChf5Y19vVGBOjqHjHOXj8MmkwB5SWkAPX49Wji9yIWNun15yDDa+dyX59JnuePz770U= X-Received: by 2002:a05:6830:20a:b0:6e4:7403:504d with SMTP id em10-20020a056830020a00b006e47403504dmr1658124otb.1.1708610052615; Thu, 22 Feb 2024 05:54:12 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Patrick Robb Date: Thu, 22 Feb 2024 08:54:01 -0500 Message-ID: Subject: Re: Email based retests for the Loongarch lab To: zhoumin Cc: ci@dpdk.org, Aaron Conole , David Marchand Content-Type: multipart/alternative; boundary="0000000000003f07920611f8c74b" X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org --0000000000003f07920611f8c74b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable And I forgot to mention, you can set up part of this using the dpdk-ci project get_reruns.py script. It polls the Rest API for all comment on patch emails events in a given timeframe, and uses regex to write a json file containing any retest requests from that period. We run this periodically (every 15 minutes) at UNH using Jenkins, but I think you could do this with a cron job or another solution. Just remember to keep bringing the timeframe parameters forward or you will end up consuming a retest request more than once! https://git.dpdk.org/tools/dpdk-ci/tree/tools/get_reruns.py On Thu, Feb 22, 2024 at 12:55=E2=80=AFAM Patrick Robb w= rote: > Hi Zhoumin, > > I wanted to reach out to you about the possibility of adding the Loongson > lab to the group of labs supporting the email based retest framework. > Currently, the UNH Community Lab and also the GitHub Robot are supporting > patch retest requests from emails, and we would like to extend that to al= l > the publicly reporting CI labs, if possible. > > For context, the original announcement: > https://inbox.dpdk.org/ci/CAC-YWqiXqBYyzPsc4UD7LbUHKha_Vb3=3DAot+dQomuRLo= jy2hvA@mail.gmail.com/ > > Aaron announcing support for the github robot: > https://inbox.dpdk.org/ci/f7tedfooq6k.fsf@redhat.com/ > > And the retest framework definition on the dpdk.org testing page: > https://core.dpdk.org/testing/#requesting-a-patch-retest > > So a format like: > > Recheck-request: iol-compile-amd64-testing, iol-broadcom-Performance, > iol-unit-arm64-testing, github-robot > > Is current accepted, and it would be great if we could add Loongson > support to the list too. What we are supporting right now is doing > retesting on the original DPDK artifact created for a patch when that pat= ch > was submitted. But we are also thinking of adding in rebasing off of tip = of > branch as a v2 feature. > > Does this sound possible for the Loonson lab? I know you are leveraging > the dpdk-ci repo for standing up your CI testing, but I don't know > specifically whether that lends itself well towards doing retests later, = or > if that would be a big technical challenge. Let me know! > > If it is possible for the Loongson lab, maybe we can discuss in the March > 7 CI Testing meeting? > --=20 Patrick Robb Technical Service Manager UNH InterOperability Laboratory 21 Madbury Rd, Suite 100, Durham, NH 03824 www.iol.unh.edu --0000000000003f07920611f8c74b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
And I forgot to mention, you can set up part of this using= the=C2=A0dpdk-ci project get_reruns.py script. It polls the Rest API for a= ll comment on patch emails events in a given timeframe, and uses regex to w= rite a json file containing any retest requests from that period. We run th= is periodically (every 15 minutes) at UNH using Jenkins, but I think you co= uld do this with a cron job or another solution.=C2=A0

J= ust remember to keep bringing the timeframe parameters forward or you will = end up consuming a retest request more than once!=C2=A0


On Thu, Feb 22, 2024 at 12:55=E2=80=AFAM Patrick Robb <probb@iol.unh.edu> wrote:
Hi=C2=A0Zhoumin,
I wanted to reach out to you about the possibility of addin= g the Loongson lab to the group of labs supporting the email based retest f= ramework. Currently, the UNH Community Lab and also the GitHub Robot are su= pporting patch retest requests from emails, and we would like to extend tha= t to all the publicly=C2=A0reporting CI labs, if possible.=C2=A0
=

=
Aaron announcing support for the github robot:=C2=A0https://i= nbox.dpdk.org/ci/f7tedfooq6k.fsf@redhat.com/

A= nd the retest framework definition on the dpdk.org testing page:=C2=A0https://core.dpdk.= org/testing/#requesting-a-patch-retest

So a fo= rmat like:

Recheck-request: iol-compile-amd64-test= ing, iol-broadcom-Performance, iol-unit-arm64-testing, github-robot

Is current accepted, and it would=C2=A0be great if we= could add Loongson support to the list too. What we are supporting right= =C2=A0now is doing retesting on the original DPDK artifact created for a pa= tch when that patch was submitted. But we are also thinking of adding in re= basing off of tip of branch as a v2 feature.=C2=A0

Does this sound possible for the Loonson lab? I know you are leveraging th= e dpdk-ci repo for standing up your CI testing, but I don't know specif= ically whether that lends itself well towards doing retests later, or if th= at would be a big technical challenge. Let me know!=C2=A0

If it is possible for the=C2=A0Loongson lab, maybe we can discuss i= n the March 7 CI Testing meeting?


--

Patrick Robb

<= span style=3D"font-size:10pt;font-family:Arial;color:rgb(0,0,0);background-= color:transparent;vertical-align:baseline;white-space:pre-wrap">Technical S= ervice Manager

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

www.iol.unh.edu


--0000000000003f07920611f8c74b--