From: Aaron Conole <aconole@redhat.com>
To: ci@dpdk.org
Cc: Michael Santana <msantana@redhat.com>,
David Marchand <dmarchan@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>,
Patrick Robb <probb@iol.unh.edu>,
Dumitru Ceara <dceara@redhat.com>
Subject: Re: [PATCH v3 0/3] Add a recheck framework to pw-ci
Date: Thu, 30 Nov 2023 11:04:15 -0500 [thread overview]
Message-ID: <f7t8r6fmdmo.fsf@redhat.com> (raw)
In-Reply-To: <20231128210155.1388785-1-aconole@redhat.com> (Aaron Conole's message of "Tue, 28 Nov 2023 16:01:51 -0500")
Aaron Conole <aconole@redhat.com> writes:
> This allows users to send repsonse emails to patches and force
> rebuilds of the workflow in github actions.
>
> This has been tested with the following:
>
> for recheck in $(./recheck_tool --pw-project=dpdk \
> --pw-instance=patches.dpdk.org \
> --filter=github-robot --state=1 | \
> jq -rc '.rechecks[]'); do
> ./github_restart --pw-project=dpdk --pw-instance=patches.dpdk.org \
> --series-id=$(echo "$recheck" | \
> jq -rc '.series_id') \
> --repository=ovsrobot/dpdk \
> --sha=$(echo "$recheck" | jq -rc '.sha') \
> --github-token=XXXXXXXX
> done
>
> And succesffully rebuilt 6457922075 from series 29774 which does have
> a recheck-request (we used the iol-unit-amd64-testing filter to do
> the test).
>
> To be added is a way to filter on specific workflows so we don't
> restart all workflows associated with the run for those projects which
> have more than one workflow.
>
> This can be combined with a second call of the recheck tool to advance
> the state. When the series id is provided, the tool will update the
> gap_sync column for the specific row and future calls to
> github_monitor script will then scan the new run.
>
> RFCv2 -> v3:
>
> - Added RECHECK.rst to cover the basic worfklow. Project specific details
> are expected to be posted to the individual projects documentation.
>
> - Moved a function for series-db-lib.sh from 3/3 to 2/3, since it was needed
> for the recheck_tool
>
> - Moved some help text from 1/3 to 2/3
>
> Aaron Conole (3):
> pw_mon: improve command line options
> recheck: Add a recheck parser for patchwork comments
> github: add a tool for restarting checks
>
> RECHECK.rst | 81 ++++++++++++++++++++++++++
> github_restart | 145 +++++++++++++++++++++++++++++++++++++++++++++++
> pw_mon | 123 +++++++++++++++++++++++++++++++++++-----
> recheck_tool | 100 ++++++++++++++++++++++++++++++++
> series_db_lib.sh | 80 +++++++++++++++++++++++++-
> 5 files changed, 513 insertions(+), 16 deletions(-)
> create mode 100644 RECHECK.rst
> create mode 100755 github_restart
> create mode 100755 recheck_tool
I applied this series. Thanks all!
prev parent reply other threads:[~2023-11-30 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 21:01 Aaron Conole
2023-11-28 21:01 ` [PATCH v3 1/3] pw_mon: improve command line options Aaron Conole
2023-11-28 21:01 ` [PATCH v3 2/3] recheck: Add a recheck parser for patchwork comments Aaron Conole
2023-11-28 21:01 ` [PATCH v3 3/3] github: add a tool for restarting checks Aaron Conole
2023-11-30 16:04 ` 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=f7t8r6fmdmo.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=dceara@redhat.com \
--cc=dmarchan@redhat.com \
--cc=msantana@redhat.com \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
/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).