ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Joerg Roedel <joro@8bytes.org>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Regression tracking
Date: Tue, 9 Aug 2016 21:02:22 +0200	[thread overview]
Message-ID: <a9abc71f-7070-3f60-3f4c-16ac7a082fc9@leemhuis.info> (raw)
In-Reply-To: <20160809094046.GA1437@8bytes.org>

On 09.08.2016 11:40, Joerg Roedel wrote:
> 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 :-/
> […] But I think
> this will also involve teaching our testers/users on how to best report
> regressions.

Yeah, definitely. One afaics important part that needs to be done in
this area: make bugzilla.kernel.org work better. At least some (or maybe
even quite a lot?) of the bugs reported there afaics seem to not get
proper attention from the right people. Due to that I'd assume some
testers will have come to conclusions like "testing for regressions and
bugs is not worth the trouble, as the kernel developers are not
interested in the bugs I file anyway".

> Part of the discussion should also be on automation, for
> example if we could/should revive the kerneloops tool?

Ugh, what's the latest status of it? I just saw
http://www.kerneloops.org/ is kind of alive again as
http://oops.kernel.org/ (I had missed that) and has data from recent
kernel versions. But it seems the code behind it hasn't seen much
changes in the last two years:
https://github.com/oops-kernel-org/kerneloops/commits/master

Side note: kernelopps and error reporting was talked about on KS2013:
https://lwn.net/Articles/571997/ ABRT was mentioned there. Fedora these
days by default installs abrt-addon-kerneloops (see
https://abrt.readthedocs.io/en/latest/supported_langs.html#linux-kernel
for a very brief intro). Things it picks up can be seen on
https://retrace.fedoraproject.org/faf/summary/ The Fedora kernel package
maintainers use the data afaik, but I don't know any more details.
Anyway: ABRT is quite Fedora/RH specific and quite heavy. IOW: it is not
something other distros can easily integrate like it happened with the
original kerneloops tool years ago.

>[...]

Ciao, Thorsten

  reply	other threads:[~2016-08-09 19:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26 14:31 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
2016-08-09 19:02       ` Thorsten Leemhuis [this message]
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=a9abc71f-7070-3f60-3f4c-16ac7a082fc9@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=joro@8bytes.org \
    --cc=ksummit-discuss@lists.linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox