From: Aaron Conole <aconole@redhat.com>
To: jspewock@iol.unh.edu
Cc: ci@dpdk.org, alialnu@nvidia.com, probb@iol.unh.edu,
Adam Hassick <ahassick@iol.unh.edu>
Subject: Re: [PATCH v3 1/1] tools: add get_reruns script
Date: Thu, 12 Oct 2023 09:00:13 -0400 [thread overview]
Message-ID: <f7tbkd4atcy.fsf@redhat.com> (raw)
In-Reply-To: <20230921195637.11369-4-jspewock@iol.unh.edu> (jspewock@iol.unh.edu's message of "Thu, 21 Sep 2023 15:55:31 -0400")
jspewock@iol.unh.edu writes:
> From: Jeremy Spewock <jspewock@iol.unh.edu>
>
> This script is used to interact with a 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>
> ---
Applied - thanks!
prev parent reply other threads:[~2023-10-12 13:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 19:55 [PATCH v3 0/1] tools: Add script for getting rerun requests jspewock
2023-09-21 19:55 ` [PATCH v3 1/1] tools: add get_reruns script jspewock
2023-10-12 13:00 ` Aaron Conole [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=f7tbkd4atcy.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=ahassick@iol.unh.edu \
--cc=alialnu@nvidia.com \
--cc=ci@dpdk.org \
--cc=jspewock@iol.unh.edu \
--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).