ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Shuah Khan <shuah.kh@samsung.com>,
	Kevin Hilman <khilman@linaro.org>,
	ksummit-discuss@lists.linuxfoundation.org,
	Tyler Baker <tyler.baker@linaro.org>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Testing
Date: Wed, 08 Jul 2015 06:52:02 -0700	[thread overview]
Message-ID: <559D2B02.9020508@roeck-us.net> (raw)
In-Reply-To: <1436347639.29626.4.camel@ellerman.id.au>

Hi Michael,

On 07/08/2015 02:27 AM, Michael Ellerman wrote:
> On Tue, 2015-07-07 at 08:25 -0700, Guenter Roeck wrote:
>> On 07/07/2015 02:24 AM, Mark Brown wrote:
>>> One thing we typically cover at Kernel Summit is some of the activity
>>> that's going on around testing upstream.  I think it'd be useful to have
>>> some more of those discussions, both in terms of making people aware of
>>> what's available and in terms of helping the people doing testing figure
>>> out what would be useful.  A lot of this is probably well suited to a
>>> workshop session between the interested people but I do think some
>>> element in the core day beyond just a readout will be useful.
>>>
>>> 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.
>
> My concern with kisskb sending emails was always that I didn't want it to
> become a spam bot. So it can send emails, but it's opt-in.
>
> The 0-day bot takes the opposite approach, ie. mails everyone without asking,
> and in hindsight that is clearly the better option in terms of getting people
> to act on the results.
>
>
>> Sharing as many test bot configuration scripts and relevant configurations
>> as possible would be quite helpful. For example, I am building various
>> configurations for all architectures, but I don't really know if they
>> are relevant.
>
> Agreed. Your buildbot is epic. I'd love to see the config for that. My local
> buildbot is running only ~40 builders, which I thought was a lot until I saw
> yours :)
>
It is on github: https://github.com/groeck/linux-build-test.

If I count correctly, it runs more than 900 builders. Major hiccup is with
caching - it collects around 10GB of logging data per month, and under
some circumstances keeps it all in memory, so after about two months it
consumes the entire 32GB of RAM on the server it is running on, and I have
to do some manual cleanup. Other than that, it runs surprisingly well.

> The kernelci.org stuff is also really interesting, that's the closest thing
> anyone has at the moment to a "proper" kernel CI setup AFAIK.
>
Agreed.

Guenter

  reply	other threads:[~2015-07-08 13:52 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07  9:24 Mark Brown
2015-07-07 13:02 ` Alexey Dobriyan
2015-07-07 13:14   ` Mark Brown
2015-07-07 18:47     ` Steven Rostedt
2015-07-07 20:46       ` Kees Cook
2015-07-07 22:02         ` Andy Lutomirski
2015-07-08 17:37           ` Mark Brown
2015-07-08 10:43       ` Mark Brown
2015-07-09 10:24       ` Masami Hiramatsu
2015-07-09 12:00         ` Steven Rostedt
2015-07-10 10:39         ` Alexey Dobriyan
2015-07-10 14:02           ` Shuah Khan
2015-07-10 14:28             ` Alexey Dobriyan
2015-07-10 15:05             ` Steven Rostedt
2015-07-10 15:54               ` Shuah Khan
2015-07-07 15:25 ` Guenter Roeck
2015-07-07 17:18   ` Mark Brown
2015-07-07 17:23     ` Julia Lawall
2015-07-07 17:24     ` Shuah Khan
2015-07-07 17:37       ` Guenter Roeck
2015-07-07 17:52     ` Guenter Roeck
2015-07-07 18:28       ` Mark Brown
2015-07-07 22:51       ` Peter Hüwe
2015-07-20 15:53     ` Mel Gorman
2015-07-20 16:39       ` Shuah Khan
2015-07-07 19:21   ` Geert Uytterhoeven
2015-07-08  7:54     ` Dan Carpenter
2015-07-08  8:37       ` Geert Uytterhoeven
2015-07-08 12:10         ` Jiri Kosina
2015-07-08 12:37           ` Josh Boyer
2015-07-08 17:32           ` Mark Brown
2015-07-12 10:21         ` Fengguang Wu
2015-07-08  9:52       ` Mark Brown
2015-07-12 11:15         ` Fengguang Wu
2015-07-13 18:34           ` Mark Brown
2015-07-14 14:22             ` Fengguang Wu
2015-07-14 15:38               ` Mark Brown
2015-07-15 14:21                 ` Fengguang Wu
2015-07-08  9:27   ` Michael Ellerman
2015-07-08 13:52     ` Guenter Roeck [this message]
2015-07-08 16:40       ` Kevin Hilman
2015-07-08 17:24         ` Guenter Roeck
2015-07-08 18:42           ` Kevin Hilman
2015-07-09  4:23         ` Michael Ellerman
2015-07-09 18:08           ` Guenter Roeck

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=559D2B02.9020508@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=dan.carpenter@oracle.com \
    --cc=khilman@linaro.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=mpe@ellerman.id.au \
    --cc=shuah.kh@samsung.com \
    --cc=tyler.baker@linaro.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