From: Takashi Iwai <tiwai@suse.de>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINER SUMMIT] Distribution kernel bugzillas considered harmful
Date: Wed, 05 Sep 2018 22:36:17 +0200 [thread overview]
Message-ID: <s5htvn3u1fi.wl-tiwai@suse.de> (raw)
In-Reply-To: <20180905201533.GA6117@chatter>
On Wed, 05 Sep 2018 22:15:33 +0200,
Konstantin Ryabitsev wrote:
>
> On Wed, Sep 05, 2018 at 09:44:23AM -0700, Laura Abbott wrote:
> >> It would be awesome to have a "bisect@home" type of thing with a
> >> similar
> >>idea like seti@home and folding@home. Have a central queue where
> >>developers can submit upstream commits and testcases, and a swarm of
> >>volunteer drones would grab and bisect-build them until the
> >>bug-introducing commit is identified and reported back.
> >>
> >>I'll totally host the hell out of this.
> >>
> >Developers usually have no problem building and bisecting kernels,
> >it's non-kernel developers who often struggle with bisection.
> >One idea that I haven't followed up on was to extend the existing
> >targets for building distro packages to just build the source
> >side of things and then take advantage of existing environments
> >(e.g. COPR) to build the package binaries. I'd love a web interface
> >that would handle some of this automatically but, again, lack of
> >resources and knowledge of web frameworks.
>
> I'm excited that kernelci.org is coming on board as a full-fledged
> Linux Foundation project, since I'm hoping that their charter would
> include funding this kind of development. [1] I was already chatting
> with Kevin about some of the cool things we could do to make various
> CI/fuzzing/bug-reporting tools more streamlined, so I'll add
> "bisecting as a service" to my list of suggestions for the glorious
> kernel CI tool of the future. :)
That sounds promising, thanks!
Takashi
next prev parent reply other threads:[~2018-09-05 20:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 10:13 [Ksummit-discuss] [MAINTAINER SUMMIT] Distribution kernel bugzillas considered harmful James Bottomley
2018-09-05 11:37 ` Mark Brown
2018-09-05 15:03 ` Paul E. McKenney
2018-09-05 15:50 ` Steven Rostedt
2018-09-05 16:20 ` Paul E. McKenney
2018-09-05 16:45 ` James Bottomley
2018-09-05 17:00 ` Paul E. McKenney
2018-09-05 19:25 ` Jiri Kosina
2018-09-05 19:40 ` James Bottomley
2018-09-06 19:54 ` Jiri Kosina
2018-09-18 13:43 ` Martin K. Petersen
2018-09-18 14:12 ` Geert Uytterhoeven
2018-09-18 15:01 ` Martin K. Petersen
2018-09-18 15:27 ` Christoph Hellwig
2018-09-18 15:34 ` Jens Axboe
2018-09-18 17:08 ` Mark Brown
2018-09-18 16:12 ` Mark Brown
2018-09-18 20:20 ` Takashi Iwai
2018-09-19 0:08 ` Mark Brown
2018-09-18 20:37 ` Takashi Iwai
2018-09-19 6:16 ` Geert Uytterhoeven
2018-09-19 6:31 ` Takashi Iwai
2018-09-19 9:23 ` Jan Kara
2018-09-19 9:27 ` Takashi Iwai
2018-09-05 13:16 ` Takashi Iwai
2018-09-05 13:20 ` Jiri Kosina
2018-09-05 13:39 ` Konstantin Ryabitsev
2018-09-05 15:16 ` Sasha Levin
2018-09-05 16:44 ` Laura Abbott
2018-09-05 20:15 ` Konstantin Ryabitsev
2018-09-05 20:36 ` Takashi Iwai [this message]
2018-09-07 20:24 ` Mauro Carvalho Chehab
2018-09-05 17:41 ` 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=s5htvn3u1fi.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=James.Bottomley@hansenpartnership.com \
--cc=konstantin@linuxfoundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).