From: Thorsten Leemhuis <linux@leemhuis.info>
To: Mark Brown <broonie@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Greg KH <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
regressions@lists.linux.dev,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Pablo Neira Ayuso <pablo@netfilter.org>,
ksummit@lists.linux.dev, workflows@vger.kernel.org
Subject: Re: RFC: building a regression tracking bot for Linux kernel development
Date: Fri, 23 Apr 2021 08:34:29 +0200 [thread overview]
Message-ID: <1390e998-4847-eebf-1d7b-e9cb6625cff7@leemhuis.info> (raw)
In-Reply-To: <20210422145107.GH4572@sirena.org.uk>
On 22.04.21 16:51, Mark Brown wrote:
> On Thu, Apr 22, 2021 at 09:16:40AM +0200, Thorsten Leemhuis wrote:
>
>> That's it already. The regression was tracked with:
>
>> * minimal overhead for the reporter
>> * no additional overhead for the developers – only something they ought
>> to do already became more important
>
> For things that are caught by the various automated systems the
> deduplication might get annoying - even for the systems with a human in
> the loop it's very common for things that the automated systems pick up
> to end up getting reported several times over due to things like race
> conditions in the reporting process. We'll have to see how that goes,
> it might be possible to automate some of it.
Yeah, good point, thx for pointing it out, will keep an eye on this
aspect to make sure it doesn't become a big problem.
Ciao, Thorsten
next prev parent reply other threads:[~2021-04-23 6:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 7:16 RFC: building a regression tracking bot for Linux kernel development Thorsten Leemhuis
2021-04-22 14:51 ` Mark Brown
2021-04-23 6:34 ` Thorsten Leemhuis [this message]
2021-04-23 10:11 ` Greg KH
2021-04-23 10:49 ` Thorsten Leemhuis
2021-04-23 11:01 ` Takashi Iwai
2021-04-23 11:11 ` Thorsten Leemhuis
2021-04-23 20:45 ` Guillaume Tucker
2021-04-24 9:43 ` Thorsten Leemhuis
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=1390e998-4847-eebf-1d7b-e9cb6625cff7@leemhuis.info \
--to=linux@leemhuis.info \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=konstantin@linuxfoundation.org \
--cc=ksummit@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=rafael@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
--cc=workflows@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.