From: Joerg Roedel <joro@8bytes.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Regression tracking
Date: Tue, 9 Aug 2016 11:40:46 +0200 [thread overview]
Message-ID: <20160809094046.GA1437@8bytes.org> (raw)
In-Reply-To: <4b6ef14c-cea6-b51d-62db-ba3e708916ea@leemhuis.info>
On Wed, Jul 27, 2016 at 02:28:26PM +0200, Thorsten Leemhuis wrote:
> On 26.07.2016 22:36, Rafael J. Wysocki wrote:
> > > There were other people trying to do that when I had stopped doing it, but
> > > they gave up eventually.
>
> Yeah, I guess that can easily happen sooner or later, because from what
> I can see it's a lot of manual and boring work that only now and then
> feels rewarding :-/
I am also interested in this one. Regression tracking is a very time
consuming task and we should discuss how that can be improved, so that
we get a sustainable solution that works for the kernel.
As Thorsten already pointed out, better tooling would help. But I think
this will also involve teaching our testers/users on how to best report
regressions. Part of the discussion should also be on automation, for
example if we could/should revive the kerneloops tool?
Just my few thoughts, but if this is goind to be discussed, I'd like to
particpate.
Joerg
next prev parent reply other threads:[~2016-08-09 9:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 14:31 [Ksummit-discuss] [CORE TOPIC] Regression tracking Takashi Iwai
2016-07-26 20:36 ` Rafael J. Wysocki
2016-07-27 12:28 ` Thorsten Leemhuis
2016-08-01 19:58 ` Thorsten Leemhuis
2016-08-09 9:40 ` Joerg Roedel [this message]
2016-08-09 19:02 ` Thorsten Leemhuis
2016-08-09 20:21 ` Takashi Iwai
2016-08-09 22:31 ` Joerg Roedel
2016-08-09 22:55 ` Rafael J. Wysocki
2016-08-09 23:20 ` James Bottomley
2016-08-10 15:11 ` Joerg Roedel
2016-08-10 12:03 ` Jani Nikula
2016-08-10 15:01 ` Joerg Roedel
2016-08-10 16:19 ` Daniel Vetter
2016-08-10 16:47 ` Laura Abbott
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=20160809094046.GA1437@8bytes.org \
--to=joro@8bytes.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=regressions@leemhuis.info \
/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.