From: Jeremy Spewock <jspewock@iol.unh.edu>
To: Aaron Conole <aconole@redhat.com>
Cc: ci@dpdk.org, alialnu@nvidia.com, probb@iol.unh.edu, ahassick@iol.unh.edu
Subject: Re: [PATCH v2 1/1] tools: add get_reruns script
Date: Wed, 27 Sep 2023 10:23:08 -0400 [thread overview]
Message-ID: <CAAA20UQbUhvtDQOucQr7-Q2XLtFTLmR8op6ypVtnmF2M+9ZdCQ@mail.gmail.com> (raw)
In-Reply-To: <f7tfs32xmoj.fsf@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]
On Mon, Sep 25, 2023 at 12:06 PM Aaron Conole <aconole@redhat.com> wrote:
> jspewock@iol.unh.edu writes:
>
> > From: Jeremy Spewock <jspewock@iol.unh.edu>
> >
> > This script is used to interact with the DPDK Patchwork API to collect a
> > list of retests from comments on patches based on a desired list of
> > contexts to retest. The script uses regex to scan all of the comments
> > since a timestamp that is passed into the script through the CLI for
> > any comment that is requesting a retest. These requests are then filtered
> > based on the desired contexts that you pass into the script through the
> > CLI and then aggregated based on the patch series ID of the series that
> > the comment came from. This aggregated list is then outputted either to
> > a JSON file or stdout with a timestamp of the most recent comment on
> > patchworks.
> >
> > Signed-off-by: Jeremy Spewock <jspewock@iol.unh.edu>
> > Signed-off-by: Adam Hassick <ahassick@iol.unh.edu>
> > ---
>
> Thanks Jeremy - I'll take a look this week. Just returning from PTO.
>
>
I actually submitted another version where you can pass in a patchworks API
URL with command-line args as well as I heard that might be useful. See v3
here:
https://patchwork.dpdk.org/project/ci/patch/20230921195637.11369-4-jspewock@iol.unh.edu/
I think I forgot to mark these other ones as outdated on patchwork, I'll be
sure to do that now.
[-- Attachment #2: Type: text/html, Size: 2453 bytes --]
prev parent reply other threads:[~2023-09-27 14:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 20:45 [PATCH v2 0/1] tools: Add script for getting rerun requests jspewock
2023-09-07 20:45 ` [PATCH v2 1/1] tools: add get_reruns script jspewock
2023-09-25 16:06 ` Aaron Conole
2023-09-27 14:23 ` Jeremy Spewock [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=CAAA20UQbUhvtDQOucQr7-Q2XLtFTLmR8op6ypVtnmF2M+9ZdCQ@mail.gmail.com \
--to=jspewock@iol.unh.edu \
--cc=aconole@redhat.com \
--cc=ahassick@iol.unh.edu \
--cc=alialnu@nvidia.com \
--cc=ci@dpdk.org \
--cc=probb@iol.unh.edu \
/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).