DPDK CI discussions
 help / color / mirror / Atom feed
From: jspewock@iol.unh.edu
To: ci@dpdk.org
Cc: aconole@redhat.com, alialnu@nvidia.com, probb@iol.unh.edu,
	Jeremy Spewock <jspewock@iol.unh.edu>
Subject: [PATCH 0/1] tools: Add script for getting rerun requests
Date: Tue,  5 Sep 2023 18:13:01 -0400	[thread overview]
Message-ID: <20230905222317.25821-2-jspewock@iol.unh.edu> (raw)

From: Jeremy Spewock <jspewock@iol.unh.edu>

As the community suggested, there should be a way for users to retest
any contexts on a given patch without needing to contact a maintainer or
resubmitting the patch. The UNH-IOL Community lab has implmented a way
to do this using the get_reruns.py script. This script is a generic way
for anyone to provide a list of contexts to filter by and a timestamp of
the time they want to consider comments since to get a
automation-friendly JSON file that contains all contexts to be rerun
grouped by the patch series ID that they should be run on. The output
JSON file also includes a timestamp of the most recent comment that was
considered so that you don't process the same data repeatedly.

The idea behind upstreaming this script is so that other labs can have
one common generic script to get the rerun information and then process
that data internally as they see fit.

Jeremy Spewock (1):
  tools: add get_reruns script

 tools/get_reruns.py | 219 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 219 insertions(+)
 create mode 100755 tools/get_reruns.py

-- 
2.41.0


             reply	other threads:[~2023-09-05 22:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-05 22:13 jspewock [this message]
2023-09-05 22:13 ` [PATCH 1/1] tools: add get_reruns script jspewock
2023-09-07 12:56   ` Aaron Conole

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=20230905222317.25821-2-jspewock@iol.unh.edu \
    --to=jspewock@iol.unh.edu \
    --cc=aconole@redhat.com \
    --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).