Re: [Ksummit-discuss] [CORE TOPIC] Testing

[Geert Uytterhoeven <geert@linux-m68k.org>]

On Tue, Jul 7, 2015 at 5:25 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>> In terms of discussion topics some of the issues I'm seeing are:
>>
>>   - Can we pool resources to share the workload of running things and
>>     interpreting results, ideally also providing some central way for
>>     people to discover what results are out there for them to look at
>>     for a given kernel in the different systems?
>>
> That might be quite useful. However, I have seen that it doesn't really
> help to just provide the test results. kissb test results have been
> available for ages, and people just don't look at it. Even the regular
> "Build regression" e-mails sent out by Geert seem to be widely ignored.

There's still a manual step involved, so I only download the logs and
generate the regression emails for every rc release.
My original plan was to automate it more, so I could run it fully automated
on the linux-next builds, too.

> What I really found to help is to bisect new problems and send an e-mail
> to the responsible maintainer and to the submitter of the patch which
> introduced it. I'd like to automate that with my test system, but
> unfortunately I just don't have the time to do it.

IIRC, kisskb used to bisect failures, but stopped doing that when it started
consuming too much time. Perhaps it can be restarted, given the system
got an upgrade a few months ago and became much much faster?
Stiil, there's the "analyzing" part.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds