From: David Marchand <david.marchand@redhat.com>
To: Aaron Conole <aconole@redhat.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Bruce Richardson <bruce.richardson@intel.com>, dev <dev@dpdk.org>,
ci@dpdk.org, Michael Santana <msantana@redhat.com>,
Lincoln Lavoie <lylavoie@iol.unh.edu>,
dpdklab <dpdklab@iol.unh.edu>
Subject: Re: [dpdk-ci] [dpdk-dev] [RFC] Proposal for allowing rerun of tests
Date: Tue, 27 Apr 2021 10:56:58 +0200 [thread overview]
Message-ID: <CAJFAV8z0=jMQrTuKg2-q5+bWKErPDc4XLAfETP8a1e-vuPB7-A@mail.gmail.com> (raw)
In-Reply-To: <f7t5z0fr884.fsf@dhcp-25.97.bos.redhat.com>
On Wed, Apr 21, 2021 at 5:03 PM Aaron Conole <aconole@redhat.com> wrote:
> >> > > First question: WHO should be allowed to ask for a re-run?
> >> > > - everybody
> >> > > - patchwork delegate
> >> >
> >> > Patchwork delegate requires to maintain a map between pw logins and an
> >> > actual mail address (if we go with email for the second point).
> >> >
> >> > > - a list of maintainers
> >> >
> >> > I'd vote on any maintainer from MAINTAINERS, _but_ it must be from the
> >> > files in the repo, not in the series being tested.
> >> > So maybe the easier is to have an explicit list... ?
>
> I agree with using the MAINTAINERS file from the repo.
>
> >> >
> >> > - author
> >> > Just listing this option for discussion, but this is dangerous, as any
> >> > user could then call reruns.
> >> >
> >>
> >> I would tend towards including this, on the basis that any author can
> >> already get a re-run just be resubmitting a new version of their patchset.
> >> This just simplifies that for all concerned.
> >
> > I agree, and it would be very convenient for authors hitting
> > a strange failure: they can double check without bothering maintainers.
>
> +1
Ok for me.
--
David Marchand
next prev parent reply other threads:[~2021-04-27 8:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 13:50 [dpdk-ci] " Aaron Conole
2021-04-13 14:47 ` Thomas Monjalon
2021-04-13 14:59 ` David Marchand
2021-04-13 15:04 ` [dpdk-ci] [dpdk-dev] " Bruce Richardson
2021-04-13 15:17 ` Thomas Monjalon
2021-04-21 15:02 ` Aaron Conole
2021-04-27 8:56 ` David Marchand [this message]
2022-01-21 14:00 ` [dpdk-ci] " Kevin Traynor
2022-01-21 17:57 ` [dpdklab] " Lincoln Lavoie
2022-01-25 13:05 ` Kevin Traynor
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='CAJFAV8z0=jMQrTuKg2-q5+bWKErPDc4XLAfETP8a1e-vuPB7-A@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--cc=lylavoie@iol.unh.edu \
--cc=msantana@redhat.com \
--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).